From e6ebfe9d7f3ce71cc99be01e3008a22816707ebd Mon Sep 17 00:00:00 2001 From: David Kalnischkies Date: Mon, 22 Jan 2018 14:38:47 +0100 Subject: add support for combination with apt-transport-mirror References: apt-transport-mirror manpage in apt --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index a7f4408..e0bc91a 100644 --- a/README.md +++ b/README.md @@ -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 -- cgit v1.2.3-70-g09d2