diff options
| -rw-r--r-- | README.md | 14 | ||||
| -rw-r--r-- | debian/links | 6 |
2 files changed, 20 insertions, 0 deletions
@@ -108,6 +108,20 @@ the second uses the default via Tor and the third uses an onion service address. Acquire::Changelogs::URI::Override::Origin::Debian "tor+http://metadata.ftp-master.debian.org/changelogs/@CHANGEPATH@_changelog"; Acquire::Changelogs::URI::Override::Origin::Debian "tor+http://cmgvqnxjoiqthvrc.onion/changelogs/@CHANGEPATH@_changelog"; +### Using apt-transport-mirror together with Tor + +apt >= 1.6 comes with a renewed mirror method which can also work correctly +with Tor: Any mirror file can be used for this by prefixing the access method +used to acquire the mirror file with `tor+`. If the mirror file is on your +local disk it should hence be `tor+mirror+file:/path/to/mirror.file` while if +it is accessed via HTTP it will look like `tor+mirror+http://example.org/path/to/mirror.file`. + +This will automatically prefix each access method mentioned in the mirror file +with `tor+`. Note that you can't specify e.g. `tor+http` in the mirror file +directly to prevent the server to detect if the client has Tor support. If you +want to include an onion service in the mirror file just use `http` as access +method for it. A client without support for Tor accessing this mirror file will +fall back to the next mirror just fine. ## Caveats diff --git a/debian/links b/debian/links index a2ffeca..6998549 100644 --- a/debian/links +++ b/debian/links @@ -1,3 +1,9 @@ +usr/lib/apt/methods/copy usr/lib/apt/methods/tor+copy +usr/lib/apt/methods/file usr/lib/apt/methods/tor+file usr/lib/apt/methods/http usr/lib/apt/methods/tor usr/lib/apt/methods/http usr/lib/apt/methods/tor+http usr/lib/apt/methods/https usr/lib/apt/methods/tor+https +usr/lib/apt/methods/mirror usr/lib/apt/methods/tor+mirror+copy +usr/lib/apt/methods/mirror usr/lib/apt/methods/tor+mirror+file +usr/lib/apt/methods/mirror usr/lib/apt/methods/tor+mirror+http +usr/lib/apt/methods/mirror usr/lib/apt/methods/tor+mirror+https |