关于通过MITM实现自定义Browser Dialer内层 HTTP host header（domain fronting）的一种猜想？
Open
Nobody has claimed this yet.
enhancement
PR welcome
- Dominant language
- Go
- Stars
- 41.7k
- Forks
- 5.9k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 29
Description
如题，对浏览器安装证书，设置代理经过core MITM之后重新发出，关于在有Proxy时特征可能不一致的问题，可以学scholar edu cn强制FakeIP
本人学艺不精，想知道一下TLS里面是否存在“如果不知道浏览器内存里面的session key等密钥就完全无法模仿”的指纹特征？
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
The issue names no files, tests, or entry points. Start by clarifying the expected Browser Dialer, MITM, proxy, and TLS behavior, then define a reproducible comparison and acceptance criteria before identifying an implementation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100