feat: add configurable PID1-owned DoH forwarding
Default managed SOCKS hostname DNS to verified HTTPS with literal-IP bootstrap and no plaintext fallback. Supervise the loopback forwarder with private anchored readiness and preserve foreign markers. Include configuration, deployment, documentation and offline checks. Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
ea886e5bc8
commit
367d956ae3
20 files changed
+2383
-37
No files matched your search
@@ -4,6 +4,13 @@
|
||||
|
||||
Go CLI for scanning and checking YouTube TLS bypass strategies with `blockcheckw`.
|
||||
|
||||
The managed target now defaults to encrypted DoH for both SOCKS hostname traffic
|
||||
and managed checks, with no plaintext fallback. Configure provider URL/bootstrap
|
||||
IPs in the private deployment `.env`; native DNS requires an explicit opt-out.
|
||||
Clients must enable SOCKS5 remote DNS (e.g. browser remote DNS on the chosen
|
||||
loopback SOCKS port). See [DNS configuration and limits](deploy/managed-target/README.md).
|
||||
This new integration is not covered by the earlier clean-run acceptance.
|
||||
|
||||
## Production preparation (isolated clean-run acceptance passed)
|
||||
|
||||
The standalone deployment candidate is a **new isolated target**, never an
|
||||
|
||||
Reference in new issue
Block a user