[Feature Request] Add tls ech protocol sniff
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 4.6k
- Avg merge
- 19d 15h
- Merged PRs (30d)
- 1
Description
Recently Russian telecom has started to block TLS 1.3 protocol with Encrypted Client Hello. It would be nice to have an option to route this traffic via proxy while sending the rest to direct. Example config that could be used with a such functionality:
"rules": [
{
"protocol": "tls-ech",
"outbound": "proxy-out"
},
]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the existing protocol-sniffing and rule-to-outbound routing entry points, then inspect how TLS traffic is classified. Done means a tls-ech rule can route matching traffic through proxy-out while other traffic remains direct, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100