Turn on encryption!

**Rart** · 10-31-2009, 12:50 AM

Could anyone explain to me exactly what this does?

Is it in some way similar to https, masking your traffic? Is it able to mask your IP? How does this differ from simply non encrypted BT?

**redMonster** · 10-31-2009, 02:20 AM

Originally Posted by Rart

Is it able to mask your IP?

That is never possible in any Bittorrent activity. Your IP always shows to the peers you connect to.

**Rart** · 10-31-2009, 02:46 AM

That's pretty much what I figured. But if not that, what kind of "encryption" is used here? Is it similar to having an https tracker? That masks your activity from your ISP only?

**pro267** · 10-31-2009, 02:52 AM

Originally Posted by Rart

Could anyone explain to me exactly what this does?

Is it in some way similar to https, masking your traffic? Is it able to mask your IP? How does this differ from simply non encrypted BT?

There are two types of connections: client to tracker connections, and client to client (p2p) connections. Both may (some say should) be encrypted.

Client to tracker connections may be encrypted using SSL encryption (https protocol), if your tracker supports that. Client to client connections may be encrypted by stream ciphers, such as RC4.

Encrypting these connections won't hide your IP address; after all, you and your peer must know the "location" (IP address) of the other party in order to be able to direct information to each other. Encryption will ensure any party along the way between you and your peer won't be able to peak into your connections and see what's going on inside. Your ISP, for instance, won't be able to know you've downloaded a .torrent file. Basically, any sort of analyzer along the way won't know what's really inside the connection you've been using. In addition, for encrypted client to tracker connections, you'll be able to authenticate that you're actually "talking" to the right tracker, and not some fake site (phishing in BT, it's plausible

).

Encryption in P2P is an extra measure of obtaining a bit more privacy and authenticity. It won't stop someone harvesting for IP addresses from connecting to a swarm and from there directly to the peers on it.

HTH.

**Rart** · 10-31-2009, 03:15 AM

Originally Posted by pro267

Originally Posted by Rart

Could anyone explain to me exactly what this does?

Is it in some way similar to https, masking your traffic? Is it able to mask your IP? How does this differ from simply non encrypted BT?

There are two types of connections: client to tracker connections, and client to client (p2p) connections. Both may (some say should) be encrypted.

Client to tracker connections may be encrypted using SSL encryption (https protocol), if your tracker supports that. Client to client connections may be encrypted by stream ciphers, such as RC4.

Encrypting these connections won't hide your IP address; after all, you and your peer must know the "location" (IP address) of the other party in order to be able to direct information to each other. Encryption will ensure any party along the way between you and your peer won't be able to peak into your connections and see what's going on inside. Your ISP, for instance, won't be able to know you've downloaded a .torrent file. Basically, any sort of analyzer along the way won't know what's really inside the connection you've been using. In addition, for encrypted client to tracker connections, you'll be able to authenticate that you're actually "talking" to the right tracker, and not some fake site (phishing in BT, it's plausible

).

Encryption in P2P is an extra measure of obtaining a bit more privacy and authenticity. It won't stop someone harvesting for IP addresses from connecting to a swarm and from there directly to the peers on it.

HTH.

Very informative! Thanks for taking the time to respond to my question.

Off topic: Whats up with your sig?