feat(hy2): implement salamander obfuscation#57
Open
FireNameFN wants to merge 4 commits into
Open
Conversation
FireNameFN
force-pushed
the
SalamanderSquash
branch
from
4115920 to
c1fa912
Compare
AkinoKaede
reviewed
Jan 28, 2026
Prevents unknown obfuscation values by validating the mode and returning an error for unsupported options, improving configuration safety and error transparency.
AkinoKaede
previously approved these changes
Jan 30, 2026
FireNameFN
commented
Jan 30, 2026
Author
|
I don't forget about this PR, just was busy. |
AkinoKaede
previously approved these changes
Jan 30, 2026
FireNameFN
commented
Feb 14, 2026
AkinoKaede
approved these changes
Feb 16, 2026
|
any update for this? |
|
Any updates? |
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
4 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.
Add Salamander obfuscation implementation for Hysteria2.
It's my first Go experience. As I know there is no need for array pooling, check it if is not true. Also it increases UDP packet size, so can make problems with MTU. Also I think that XORing can be SIMDed and hash of first part (that contains key) can be precomputed.
It is working on my setup. Tests are broken so can't run them.
Closes daeuniverse/dae#904
Closes daeuniverse/dae#798