Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

anonymous seeding and public-swarm fallback policies #885

Closed
synctext opened this issue Oct 3, 2014 · 5 comments
Closed

anonymous seeding and public-swarm fallback policies #885

synctext opened this issue Oct 3, 2014 · 5 comments

Comments

@synctext
Copy link
Member

synctext commented Oct 3, 2014

Tribler should "just work", also when we add anonymity features.
Problem: only a few users will use anonymous seeding initially.

We will (soon) offer a fully anonymous "perfect dark" downloads from anonymous sources using introduction points, rendezvous tunnels, and end-to-end encryption. Traditional unsafe seeding will be disabled by default, in favor of "no unprotected public seeding".

However, our anonymous seeding method will have zero or only a few seeders in the beginning. This bootstrap problem killed a lot of other projects. Without a smooth migration path "perfect dark" downloads are not realistic. A lot of users will get disappointed if they try to download stuff, but nothing works due to the lack of anonymous seeders.

Anonymous downloading can be done from either: unprotected public seeders and hidden seeders. The downloader is protected using various layers of proxies. When the "perfect dark" option fails we need a fallback option: anonymous downloading from public seeds.
In case an anonymous download from anonymous sources fails to make any progress after 180 seconds of trying, the fallback option will kick in and activate proxied downloading using exit nodes from public seeders. The fallback option will be enabled by default and can easily be disabled.

@synctext synctext added this to the V6.4 anonymous streaming and hidden seeding test milestone Oct 3, 2014
@Arceliar
Copy link

Arceliar commented Oct 3, 2014

I'm not sure I understand the intended use cases for anonymous downloads with a fallback. If you need anonymity, you'd want to disable fallback... and if you don't need anonymity, then you'd probably see performance gains from downloading publicly. The main use case I can think of is to generate as much anonymous cover traffic as possible (for other users to hide in) without impacting one's ability to download. I think that's a good enough reason to do it, but I'm curious if there was something else in mind...

@synctext
Copy link
Member Author

@Arceliar Thank you very much for these comments. We're working on the code right now, this ticket is unclear and use-case is not properly specified. I'll edit the ticket+add your cover traffic argument.

@synctext
Copy link
Member Author

@Arceliar finally polished the text of this ticket.

@Arceliar
Copy link

@synctext thanks, the new text makes things much clearer.

@synctext synctext modified the milestones: V8.0: end-to-end anonymity (full darknet with anonymous seeding and e2e encryption), V7.0 anonymous downloading Nov 3, 2014
@synctext
Copy link
Member Author

Clarification: we now have exit nodes. They can download existing public Bittorrent swarms. Through exit nodes this content becomes available in the encrypted "perfect dark" space.

@synctext synctext modified the milestones: V8.0: end-to-end anonymity, V9.9: Shadow Internet Feb 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants