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?
Printable View
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?
That is never possible in any Bittorrent activity. Your IP always shows to the peers you connect to.Quote:
Originally Posted by Rart
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?
There are two types of connections: client to tracker connections, and client to client (p2p) connections. Both may (some say should) be encrypted.Quote:
Originally Posted by Rart
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 :lol:).
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.Quote:
Originally Posted by pro267There are two types of connections: client to tracker connections, and client to client (p2p) connections. Both may (some say should) be encrypted.Quote:
Originally Posted by Rart
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 :lol:).
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.
Off topic: Whats up with your sig?
Actually, it is somewhat connected to the subject of this thread :whistlingQuote:
Originally Posted by Rart
Anyone can explain what exactly is that "cryptoport tracker extension" option in Vuze?
Thanks. my dl speed did improve a lot. I had no clue about this....:blink::D
How can I do this on transsmision?
I knew that when the line is encrypted the internet speed is much slower.