-
Notifications
You must be signed in to change notification settings - Fork 287
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
Add AES-256-GCM support to the new protocol #360
Open
gsliepen
wants to merge
10
commits into
1.1
Choose a base branch
from
feature/alt-ciphersuite
base: 1.1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsliepen
force-pushed
the
feature/alt-ciphersuite
branch
from
April 10, 2022 12:30
9669def
to
485108a
Compare
gsliepen
force-pushed
the
feature/alt-ciphersuite
branch
from
April 21, 2022 18:41
485108a
to
f4db140
Compare
gsliepen
added
enhancement
New feature requests or performance improvement.
1.1
Issue related to Tinc 1.1
labels
May 26, 2022
This also adds a simple cipher suite negotiation, where peers announce the ciphers they support, and their preferred cipher. Since we need to bump the SPTPS version anyway, also prefer little endian over network byte order.
…ersion. This is necessary so our copy of Chacha20-Poly1305 is compatible with that of many other crypto libraries. This code is made by Grigori Goronz, but is heavily based on the code from D.J. Bernstein's ref10 implementation used before.
Remove mentions of it from the documentation, but keep supporting the option for now, as this makes it easier to test compatibility with the legacy protocol.
The crypto library on Windows exposes a symbol named poly1305_init(), which clashes with ours. We can avoid this by moving poly1305_get_tag() to poly1305.[ch], where it belongs better, and this allows us to make all the lower-level Poly1305 functions static. Also remove the support for associated data while we are at it, since we are never using it.
gsliepen
force-pushed
the
feature/alt-ciphersuite
branch
from
May 29, 2022 16:06
f4db140
to
e994222
Compare
This is still a big blocker for us in moving to 1.1 from 1.0 It looks like there is now cipher selection / negotiation. Whats blocking? The test logs don't exist any more so perhaps @gsliepen can enlighten. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.