[tor-talk] Padding effective against simple passive end-to-end correlation attacks?

[The Doctor]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/26/2013 10:29 PM, Raynardine wrote:

> I did not realize that Bitcoin was capable of accepting incoming 
> connections via Tor. This should be a standard feature of the
> mainline Bitcoin client.

If I recall correctly, the reference implementation of the Bitcoin
protocol (https://github.com/bitcoin/bitcoin) has an option in the
config panel to set a proxy (which just happens to be localhost:9050),
protocol SOCKS5 (but it supports SOCKS4).  By checking the tickybox,
the Bitcoin client uses Tor to proxy its connections.

There is also a -tor command-line option which defaults to whatever
the -proxy command-line option defaults to (source: `bitcoin-qt --help`)

Or at least, the copy I have in front of me at this time does.  I may
very well have configured it to use Tor ages ago and forgotten that I
did.  Sanity check, anybody?

- -- 
The Doctor [412/724/301/703] [ZS|Media]
Developer, Project Byzantium: http://project-byzantium.org/

PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F  DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/

"May all your good dreams and fine wishes come true!" --Mike Jittlov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEG8IYACgkQO9j/K4B7F8HeOgCgpLkXFp426yy3W6sJbecXeqQF
sZkAoMcvA4dJ53XN5rhIT9LpvgCY9CUV
=lrcV
-----END PGP SIGNATURE-----