<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
On 01/06/2014 04:08 PM, e-letter wrote:<br>
<span style="white-space: pre;">>
(<a class="moz-txt-link-freetext" href="https://lists.cypherpunks.ca/pipermail/otr-users/2012-November/002133.html">https://lists.cypherpunks.ca/pipermail/otr-users/2012-November/002133.html</a>):<br>
>> australia111 at hushmail.com:<br>
>>> Hi<br>
>>><br>
>>> Anyone know how to use TOR + socks with Pidgin + OTR
?<br>
>>> Can it be done?<br>
>>><br>
>><br>
>> This website has a reasonable guide:<br>
>><br>
>> <a class="moz-txt-link-freetext" href="https://help.riseup.net/en/pidgin">https://help.riseup.net/en/pidgin</a><br>
>><br>
>> Current versions of Pidgin have a proxy type called
"Tor/privacy proxy"<br>
>> - simply enter the SOCKS proxy information (eg: 127.0.0.1
on port 9050 )<br>
><br>
> The guide does not indicate where the sign-in credential
originate.<br>
><br>
> According to torsocks, pidgin can be used with:<br>
><br>
> usewithtor pidgin<br>
><br>
> and the pidgin connection setting is 'no proxy' in which
case, there<br>
> does not seem to be a need to configure pidgin socks
settings?<br>
></span><br>
<br>
Actually. I wouldn't recommend using Pidgin with 'usewithtor'. The
latest versions of Pidgin has a very specific functionality build in
to handle DNS leaks over Tor! As can be seen in this screenshot I
took: <a class="moz-txt-link-freetext" href="http://i.imgur.com/trUwsi9.png">http://i.imgur.com/trUwsi9.png</a><br>
<br>
If you want to connect to a hidden service, for example the
jabber.ccc.de hidden service I use the following configuration:
<a class="moz-txt-link-freetext" href="http://i.imgur.com/33lsZEY.png">http://i.imgur.com/33lsZEY.png</a><br>
<br>
I hope this helps.<br>
<br>
All the best,<br>
Jurre<br>
<br>
<br>
- -- <br>
<a class="moz-txt-link-freetext" href="http://jurrevanbergen.nl/">http://jurrevanbergen.nl/</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.12 (GNU/Linux)<br>
<br>
iQEcBAEBAgAGBQJSytnLAAoJELc5KWfqgB0CRf0H/1ICN2elubsfb/IuMoe+/rHz<br>
wKxyIpFcq97I3OjYAlrxl5+E6SVtRYo7r7tsvMTR6TpCxlQ8XnAv0cHSNkk8oRqh<br>
zVgs+fNLXqDWFCUEosUjtncWHPBayTlgqIQhKiIKmXfFQZK9yIiPf8rdOZZgWXSy<br>
IH1UTG1rpCHZ3rpdoqj0gurxngN/Tu+h1kRWZLt2W400owaQ34MvqhTeMfj2xnpH<br>
hc895u4iBaJm61iNYeYX7Dl1K+a5+kduy1SM7ofYyRR39cq9MU8ux4MNDlDu1cQR<br>
TtuGCSm238CQP2sK8WiYgVbt8Q2jha5wRfwP2E7S9aA2ZL5bWpfYYsPxsXCxaDE=<br>
=4PKT<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>