summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-05-24 20:31:30 +0000
committerNick Mathewson <nickm@torproject.org>2007-05-24 20:31:30 +0000
commit703bf1962068a2beb8754f9bb772efd7eb3c100d (patch)
tree4fa9db1792fad7b4bcc36f2ff466f9033549eaca /ChangeLog
parent17830bc03ba26dc90258f436fbd9786cf769027c (diff)
downloadtor-703bf1962068a2beb8754f9bb772efd7eb3c100d.tar.gz
tor-703bf1962068a2beb8754f9bb772efd7eb3c100d.zip
r12942@catbus: nickm | 2007-05-24 16:31:22 -0400
Well, that was easier than I thought it would be. Tor is now a DNS proxy as well as a socks proxy. Probably some bugs remain, but since it A) has managed to resolve one address for me successfully, and B) will not affect anybody who leaves DNSPort unset, it feel like a good time to commit. svn:r10317
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 83b6613d79..dcf455c250 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -22,6 +22,12 @@ Changes in version 0.2.0.1-alpha - 2007-??-??
logging information that would be very useful to an attacker.
- Start work implementing proposal 103: Add a standalone tool to
generate key certificates.
+ - Initial implementation of a client-side DNS proxy feature to replace
+ the need for dns-proxy-tor: Just set "DNSPort 9999", and Tor will
+ now listen for DNS requests on port 9999, use the Tor network to
+ resolve them anonymously, and send the reply back like a regular DNS
+ server. The code is still buggy, undocumented, and only implements
+ a subset of DNS.
o Security fixes:
- Directory authorities now call routers stable if they have an