fix: preserve shadow-tls in-user for snell listeners#2934
Merged
Conversation
2e1bf39 to
b9ebcf6
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Snell listeners using ShadowTLS v3 now preserve the authenticated user name in inbound metadata, so
IN-USERrules can match the ShadowTLS user the same way they already do for Shadowsocks listeners.The Snell ShadowTLS handler now reuses the existing sing context additions path instead of dropping the authenticated user before Snell request metadata is built.
Test plan
go test ./listener/... -count=1