[tor-dev] N reasons why the spooks love Tribler (Number N' will surprise you)

[str4d]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Yawning Angel wrote:
> Hello all,
> 
> Recently a decentralized onion-routing based Bittorrent client
> known as Tribler has made rounds through the clickbait
> garbage^w^wtech journalism sites. Since protocol design is a
> research interest of mine, I did some casual analysis based off the
> documentation and publicly available source code.

Thank you for taking the time to write this; I'm sure I speak for many
when I say that your contributions are greatly appreciated :)

If this is "casual analysis", I shudder to think what you would find
during office hours :-P Perhaps it could be posted on the Cryptography
Coding Standard wiki [0] as an example of what not to do?

> Most of the fixes require major revisions to the wire protocol.
> As it appears that there is no versioning, how that will be done
> is left as an exercise for the student.
> 
> Alternatively, rebase the system on I2P.

If they did choose to rebase on I2P, they would be able to integrate
with the existing I2P torrent swarms. In case the Tribler developers
are following this ML, the protocol details common to all BitTorrent
clients on I2P are documented in [1].

str4d

[0] https://cryptocoding.net/
[1] https://geti2p.net/en/docs/applications/bittorrent
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUlV4AAAoJEIA97kkaNHPnZFoP/iSsUzDBUsgApq6XC0o3TMlt
SpjTEvYkuK4xq2wLEcggu+eX7ZOTQFLPjIocIfSkkPuj4DDT0/Esyg9/Fo55BsmQ
xHN6u6CaaDNCe2VdnCm1T93MFUL9hTIvVV+hXaF78QIrbp2+g5swOpuBl8ePnMhX
+YcBQ/T3mPMhKSBbDAQgRMl5vYovpu2ET2dYb0hhJcwtZ0OVSKlRSH0NJCrCH/KB
UpJCI4gSj731POUhuKVUE6oYc6ZlUJt6262sRFAyLOuej+gHlcYtXrsNjX1zOKTV
/vs0X6DeyYJlLD6gfNpZuDVZNA/a0zRJTuoK0imHwFIUQDuIXqPq3yTs8xcFcCtS
5PWjQKXgrOfN/ifwTqRaQHKm9UXaOFAkNDCfjGui+cftncZ0VquJBnsQFW6KbngK
N+1+QetXk8RQ36IyBq9H7j6uqSMTfPQiBVUFWec9GcqWaruLRRcLj5IGFTHgiAGt
KYd6bYgMFwUUTVVOTj0dgeeCqfFBdzR12rSzb3SzlXq/i8UgFcuIn5cw5p3TfWYm
LN6twG5i8tK6F2U6TNaakbmih6xMVRMUBbV/EleBrIYdQeTYG8FvAsGQQ70r0kzz
nBCiuAWYRN7EWNtmKClNJGj0GTe4gwN+0et6g0HmVqMerw+4tPAJ8exWvuJNT0e8
0EYzbEfMRcG61zVgNIPI
=xhxt
-----END PGP SIGNATURE-----