Remove obsolete fast_tls #274
Merged
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
NelsonVides
force-pushed
the
deps/fast_tls_removal
branch
5 times, most recently
from
b5ba493 to
5b92b1a
Compare
|
@NelsonVides: tls-unique and tls-server-end-point are supported too? |
Not at the moment, tls-exporter is the best option so I prioritised only that one for now. |
|
Can you add tls-server-end-point for a best compatibility too? |
NelsonVides
force-pushed
the
deps/fast_tls_removal
branch
from
ceba826 to
805bd52
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.
Also implement tls-exporter channel binding for TLSv1.3.