[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Bittorrent

On Fri, February 20, 2009 15:02, Freemor wrote:
> but what gets reported to the tracker is your actual IP
> as without that the other peers would be unable to connect to you.
It's not that simple.

I've just took a look at
http://jonas.nitro.dk/bittorrent/bittorrent-rfc.html it's the first hit on
"bittorrent rfc", I hope it's ok :-P
As you can see at
http://jonas.nitro.dk/bittorrent/bittorrent-rfc.html#anchor18 the "ip"
field is totally optional (many bt clients let you specify your real ip,
usually after you enable a proxy setting), the tracker will identify your
client with the "peer_id", the "port" values and what you need from / have
to offer to the swarm.
The tracker response
(http://jonas.nitro.dk/bittorrent/bittorrent-rfc.html#anchor19) will send
you a list of peer_id/ip/port and your own entry will be composed of your
peer_id and and (non torified) port with the exit node ip.
Data exchange is described at
http://jonas.nitro.dk/bittorrent/bittorrent-rfc.html#anchor21 as you can
read the peers only check if the peer_id is a valid one (it is in the
tracker response), not if the ip address is a known one, in this way you
keep on reporting torified ips to the tracker and the real ip to the
clients you connect to.

Unless trackers will start accepting id/ip "corrections" from clients
(quite useless as it can lead to serious swarm damage as there's no strong
authentication mechanism) this method will grant you some anonymity.


Marco Bonetti
BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/
My webstuff: http://sidbox.homelinux.org/

My GnuPG key id: 0x86A91047