mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-24 14:51:11 +01:00
Changes file for new DNS caching options
This commit is contained in:
parent
bde6f2daba
commit
522e90d661
1 changed files with 21 additions and 0 deletions
21
changes/prop205-simplified
Normal file
21
changes/prop205-simplified
Normal file
|
@ -0,0 +1,21 @@
|
|||
o Major features:
|
||||
|
||||
- The updating and usage of DNS cache is now configurable on a
|
||||
per- client-port level. SOCKSPort, DNSPort, etc lines may now
|
||||
contain {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we
|
||||
shouldn't cache these types of DNS answers when we receive them
|
||||
from an exit node in response to a request from this port, and
|
||||
{No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
|
||||
cached DNS answers of these types, we shouldn't use them. It's
|
||||
potentially risky to use cached DNS answers at the client,
|
||||
since doing so can indicate to one exit
|
||||
what answers we've gotten for DNS lookups in the past. With
|
||||
IPv6, this becomes especially problematic. Using cached DNS
|
||||
answers for requests on the same circuit would present less
|
||||
linkability risk, since all traffic on a circuits is already
|
||||
linkable, but it would also provide little performance benefit:
|
||||
the exit node caches DNS replies too. Implements a simplified
|
||||
version of Proposal 205.
|
||||
|
||||
|
||||
|
Loading…
Add table
Reference in a new issue