Use tls-crypt instead of tls-auth #501
Open
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
|
This is great, thanks! |
|
Any estimate on when we will see this merged? |
GHOSCHT
added a commit
to GHOSCHT/docker-openvpn
that referenced
this pull request
May 20, 2021
BirdDev
added a commit
to BirdDev/docker-openvpn
that referenced
this pull request
Nov 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With tls-crypt, all TLS protocol related packets (including handshakes, user authentication, config push, etc.) are encrypted and authenticated with the key from the static key file. This helps to hide the fact that it's an OpenVPN TLS connection, which is critical for people using it for circumventing censorship in suppressive countries like China or Iran.