Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Probe Shadowsocks #445

Open
yrutschle opened this issue Jun 2, 2024 · 2 comments
Open

Probe Shadowsocks #445

yrutschle opened this issue Jun 2, 2024 · 2 comments

Comments

@yrutschle
Copy link
Owner

          This is totally off topic, but similar, read how the GFW passively blocks Shadowsocks proxies. Would be best to implement the reverse of it into sslh though:

https://gfw.report/publications/usenixsecurity23/en/

Originally posted by @iamdoubz in #316 (comment)

@yrutschle
Copy link
Owner Author

@iamdoubz I am not sure what you suggest: heuristics to determine if random-looking traffic is Shadowsocks? (I admit I haven't read the whole paper. I might in the coming weeks, but no guarantees)

@iamdoubz
Copy link
Contributor

iamdoubz commented Jun 4, 2024

The simple version is use what the paper explores to determine if the tls traffic is obfuscated on purpose and forward that traffic to another service inside of the sslh.cfg file. Would be a "catch all" tls traffic of sorts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants