-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable TLS connections between peers #68
Conversation
all tests passed |
@kentsommer this looks really cool! Can you tell which version of OpenSSL does it support or require? Also, there is a fork of OpenSSL called BoringSSL, maintained by Google/Cloudflare/etc that is mostly source-compatible with OpenSSL and is much better maintained/fuzzed/secured and would provide a smaller attack surface on TLS-enabled hush nodes : https://boringssl.googlesource.com/boringssl/+/HEAD/PORTING.md Could you estimate if it would be hard or relatively easy to support BoringSSL? Many projects try to detect various SSL libraries in a certain order, I would prefer BoringSSL over OpenSSL, if both are installed. |
Rebasing to merge into dev |
all tests passed |
@kentsommer Can we include the changes requested in Discord, then rebase for merge? Pasting below for visibility. We need proper display of secure peers in both
Please commit those changes, rebase, merge to dev :). |
Requested changes added by dda2c82
|
See
SECURE_SETUP.md
for documentation on new flags + how to set up a node with its own valid certificate.t1JjmKWun4jn61JgVSK1fQKifVToqhKsov3