Task #2367
add tor support to F-Droid client
| Status: | Closed | Start date: | 11/06/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | hans | % Done: | 0% | |
| Category: | - | |||
| Target version: | new unified Downloader infrastructure | |||
| Component: |
Description
F-Droid client should work with tor. The support should be something like this:
- add manual proxy settings
- add "use Tor" checkbox via OnionKit
- automatically support .onion addresses regardless of proxy settings/use tor
Related issues
Associated revisions
add TorHttpDownloader for handling repos on Tor Hidden Services
Tor Hidden Services are on domain names that always end in .onion, so there
is a URL pattern matcher that chooses which Downloader subclass to use
based on testing for .onion. This is a quick, dumb implementation. It
does make any attempt to see if Tor is running or even installed. That
can come once NetCipher is easy to handle in the context of FDroid.
implemented IconDownloader for UIL downloads with FDroid classes
This lets UniversalImageLoader (UIL) use FDroid's generic Downloader
infrastucture so that connection configuration all happens based on the URL
in DownloaderFactory.
refs #2598 https://dev.guardianproject.info/issues/2598
refs #2367 https://dev.guardianproject.info/issues/2367
add "HTTP Proxy" preference to support Tor, I2P, or any other proxy
This is the most basic support for channeling all downloads through Tor or
I2P. This does not include Orbot integration, so the use will have to know
to start Orbot before using this. I don't know anything about I2P.
closes #2367 https://dev.guardianproject.info/issues/2367
https://f-droid.org/repository/issues/?do=view_issue&issue=404
https://f-droid.org/repository/issues/?do=view_issue&issue=424
History
#1 Updated by hans about 4 years ago
issue on F-Droid tracker: https://f-droid.org/repository/issues/?do=view_issue&issue=404
#2 Updated by hans about 4 years ago
one use case would be to setup an old device somewhere that has access to good update channels, whether its F-Droid or the Google Play Store, or others. This device would update itself from those channels, then share its installed APKs via Kerplapp over a Tor Hidden Service. Then devices that are roaming in places where the good update channels are blocked could use this Hidden Service to keep up-to-date.
#3 Updated by hans about 4 years ago
- Target version set to improved security/usability
#4 Updated by hans about 4 years ago
another related upstream issue: https://f-droid.org/repository/issues/?do=view_issue&issue=424
#5 Updated by hans over 3 years ago
- Target version changed from improved security/usability to 134
#6 Updated by hans over 3 years ago
- Target version changed from 134 to new unified Downloader infrastructure
#7 Updated by hans over 3 years ago
- Status changed from New to In Progress
#8 Updated by Anonymous over 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset fdroidclient|commit:b7f0195234713cd22851e0100500ad7cec6184e8.
#9 Updated by hans over 3 years ago
- Status changed from Resolved to Closed