Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Forcing encryption in torrent extention #7788

Open
srirambv opened this issue Mar 20, 2017 · 2 comments
Open

Forcing encryption in torrent extention #7788

srirambv opened this issue Mar 20, 2017 · 2 comments

Comments

@srirambv
Copy link
Collaborator

From community https://community.brave.com/t/forcing-encryption-in-torrent-extention/1755

Not that I use it regularly but I think Brave should deploy the torrent extension with 'Force encryption' as a prerequisite and any other security and privacy features upon advice of the community.

cc: @feross

@feross
Copy link
Contributor

feross commented Mar 20, 2017

I can take a look at what it takes to implement this when I'm in the office on Thursday. From what I've heard, torrent encryption does not offer much in the way of true privacy or security. It's more like packet obfuscation to make it harder for hostile ISPs to identify traffic as BitTorrent. Doesn't hurt to look into it further though.

@feross feross self-assigned this Mar 20, 2017
@cezaraugusto cezaraugusto added this to the Triage Backlog milestone Nov 8, 2017
@NumDeP
Copy link

NumDeP commented Dec 26, 2017

I figured (for others) it would be helpful for research purposes to post the link related to other clients, protocols and their supported features -

One thing I didn't know before viewing the link above was that choosing Forced Encryption sort of deprives a user of a greater number of peers, though I think given certain revelations regarding the data industry, I think many if not most connect to encryption-enabled peers now-a-days and thus generate a greater number of peers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants