aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorPeter Palfrader <peter@palfrader.org>2009-01-18 01:05:17 +0000
committerPeter Palfrader <peter@palfrader.org>2009-01-18 01:05:17 +0000
commit0636369b83f9a31dc9324ee10f1a3d20e290c963 (patch)
tree407244fa7d24b6ae0259db3330f789007bff83d6 /ChangeLog
parent58110054427a74075c28e78345005ad9546b612c (diff)
downloadtor-0636369b83f9a31dc9324ee10f1a3d20e290c963.tar.gz
tor-0636369b83f9a31dc9324ee10f1a3d20e290c963.zip
mention that tsocks only socksifies TCP
In the torify(1) manpage explain that tsocks will only socksify TCP connections, and that therefore it will most likely leak DNS requests. svn:r18160
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog2
1 files changed, 2 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 6d8af9f295..f6d29cf39f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -24,6 +24,8 @@ Changes in version 0.2.1.11-alpha - 2009-01-??
cell back), avoid using that OR connection anymore, and also
tell all the one-hop directory requests waiting for it that they
should fail. Bugfix on 0.2.1.3-alpha.
+ - In the torify(1) manpage mention that tsocks will leak your
+ DNS requests.
Changes in version 0.2.1.10-alpha - 2009-01-06