Skip to content

Enabled switching between tls and net package#6

Open
GammaSQ wants to merge 4 commits intocryptocoinjs:masterfrom
GammaSQ:pullCompliant
Open

Enabled switching between tls and net package#6
GammaSQ wants to merge 4 commits intocryptocoinjs:masterfrom
GammaSQ:pullCompliant

Conversation

@GammaSQ
Copy link

@GammaSQ GammaSQ commented Jan 27, 2015

A simple enhancement to allow the connection to be encrypted. Tests are passing.
Weather tls or net is used can be set with a boolean in the settings.js and test-settings.js file.
(I felt like having settings for the tests split from general settings. Both settings still have to carry the same useTLS-setting!)
There is not yet an automated test to run all tests once with tls and once with net enabled.
To implement a switch dependent on cryptocoinjs/coininfo, it can be required within the settings.js.

@GammaSQ
Copy link
Author

GammaSQ commented Feb 11, 2015

I just found out that node version 11.3 introduced a TLSSocket-class. This means that my cleartextStream-check will fail! So please run tests with node.js < 0.11.3 !
So far I don't know when I will upgrade the code. (This has some uncomfortable implication for the Host-object ... needs some thinking ... )

@GammaSQ
Copy link
Author

GammaSQ commented Feb 12, 2015

Host-object now has a .TLS boolean. The .socket attribute is always used to save the cleartextStream/TLSSocket (if useTLS == true).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant