ProxymanApp / ProxymanApp/Proxyman
Breaks with encrypted DNS on Big Sur
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Proxyman version?
Version 2.14.1 (21410)
macOS Version?
11.0.1 (20B29)
Steps to reproduce
- Install configuration profile that configures the native encrypted DNS feature new to Big Sur (I am using NextDNS), other examples → https://github.com/paulmillr/encrypted-dns
- Launch Proxyman
Now all traffic is blocked. The only way to use Proxyman now is to disable the networks service that was installed by the profile in System Preferences → Network.
I don't know how the new encrypted DNS works internally or if it is even possible for Proxyman to work in such a setup. Happy to provide more info if needed 😊
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
Start by reproducing the issue on macOS 11.0.1 with a native encrypted DNS configuration profile such as NextDNS, then launch Proxyman and inspect the installed service in System Preferences → Network. Done means Proxyman can capture traffic without requiring the encrypted-DNS network service to be disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100