-
Notifications
You must be signed in to change notification settings - Fork 15
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
use wireguard for tunnels #39
Labels
Comments
@axn what cryptographic primitives are you currently using? |
This issue is handled by me for the purposes of Google Summer of Code 2019.
For any clarification on the approach, tips for the implementation or requested functionality, please comment on this thread. |
I assigned the issue to you, make us proud! |
Progress Update:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
connections between nodes are mostly via unencrypted wireless connections. to add some security it would be reasonable to encrypt tunnel connections. these happen mostly between a node and a uplink gateway the client trusts.
the current tunnel plugin could be rewritten to use wireguard or an addition plugin is used, as wireguard slows throughput on devices with low resources
the public keys should be announced via descriptive messages
generally it could be worth some research to change the current crypto keys to the ones used by wireguard
The text was updated successfully, but these errors were encountered: