Add support for TLS client certificate auth #357
Closed
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
|
If the maintainer is willing to merge this, I'll add update the doc in another commit. |
nekohasekai
force-pushed
the
dev-next
branch
9 times, most recently
from
6b37ba1
to
22bf7a9
Compare
nekohasekai
force-pushed
the
dev-next
branch
7 times, most recently
from
50085f1
to
a2d43b3
Compare
nekohasekai
force-pushed
the
dev-next
branch
8 times, most recently
from
2833928
to
5a4e8fe
Compare
nekohasekai
force-pushed
the
dev-next
branch
4 times, most recently
from
125329c
to
8a9cb08
Compare
nekohasekai
force-pushed
the
dev-next
branch
3 times, most recently
from
0d5b079
to
f46732b
Compare
nekohasekai
force-pushed
the
dev-next
branch
9 times, most recently
from
7f672ec
to
e91a6e5
Compare
nekohasekai
force-pushed
the
dev-next
branch
17 times, most recently
from
1f5302a
to
33026e1
Compare
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.
The primary purpose is to defeat active probing, since any probes will fail at TLS handshake and not be able to further test the underlying application protocol.
TLS client authentication is not used often on the Internet, but most of the users are big companies, so I don't think its presence will trigger more stringent blocking.