summaryrefslogtreecommitdiffstats
path: root/wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn')
-rw-r--r--wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn b/wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn
new file mode 100644
index 0000000..4c2cd86
--- /dev/null
+++ b/wiki/src/bugs/claws_with_torsocks_leaks_hostname.mdwn
@@ -0,0 +1,9 @@
+In Tails 0.12 we introduced `torsocks` as a replacement for `tsocks`
+used by the `torify` script. The switch to `torsocks` made Claws Mail,
+which is started using `torify`, leak the hostname in the HELO/EHLO
+message, resulting in a hostname leak in the `Message ID` and
+`Received` email headers. This is currently being worked around by
+switching back to `tsocks` for Claws Mail only (in branch
+`bugfix/claws_vs_torsocks`) but the fact that `torsocks` behaves worse
+than `tsocks` in this respect is worrying and should be investigated
+further. Perhaps other applications using `torify` are also affected?