You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This idea would require a major redesign of how Tallow handles DNS. Currently, DNS requests are serviced by Tallow itself, which then forwards the domain over SOCKS4a. So it is left to the Tor exit node to do the real name resolution. This approach is fast, since DNS requests are serviced "instantly".
An alternative DNS mode would be to tunnel the request over Tor (must be TCP), e.g., to a service like DNSCrypt. Next, the TCP connection is established using SOCKS4. This mode is slower, but allows the user to choose the name resolution service.
Ideally, both modes could be supported, so this is an interesting project. However, the usual problem is that my time is very limited...
Hi,
I want to encrypt my DNS traffic, so can you add this feature to Tallow, Reqrypt.
Add "Forces SOCKS4" + "DNSCrypt" features.
"SOCKS4 + dnscrypt-proxy: Forward the DNS traffic to a DNS server which I choose. Although the DNS server is DNSSEC, DNSCrypto and has no logs."
Learn more: https://tor.stackexchange.com/questions/1503/dnssec-dnscrypt-over-tor
I think DNSCrypt+Reqrypt is not bad idea too.
The text was updated successfully, but these errors were encountered: