aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-11-25 16:38:29 -0500
committerNick Mathewson <nickm@torproject.org>2012-12-17 14:49:38 -0500
commit522e90d6610da3ca809c842b452c56ecab5d501b (patch)
tree6000b6885edf088baca50b913fd37bc7f0cc9b71 /changes
parentbde6f2daba59fc75ec32d91e2a29f8d21a08d487 (diff)
downloadtor-522e90d6610da3ca809c842b452c56ecab5d501b.tar
tor-522e90d6610da3ca809c842b452c56ecab5d501b.tar.gz
Changes file for new DNS caching options
Diffstat (limited to 'changes')
-rw-r--r--changes/prop205-simplified21
1 files changed, 21 insertions, 0 deletions
diff --git a/changes/prop205-simplified b/changes/prop205-simplified
new file mode 100644
index 000000000..c764fea8e
--- /dev/null
+++ b/changes/prop205-simplified
@@ -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.
+
+
+