[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#759341: marked as done (use a separate tor circuit for each sources.list line)

Your message dated Mon, 3 Oct 2016 22:24:13 +0200
with message-id <20161003202412.p6lwkq2hx34dslnu@crossbow>
and subject line Re: use a separate tor circuit for each sources.list line
has caused the Debian Bug report #759341,
regarding use a separate tor circuit for each sources.list line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
759341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759341
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt-transport-tor
Version: 0.2.1-1
Severity: wishlist

apt-transport-tor should use a separate tor circuit for each line in
sources.list. Otherwise it may be possible for exit nodes to
fingerprint systems based on the set of sources.lists lines they use.

--- End Message ---
--- Begin Message --- 
Version: 0.3

Hi,

On Tue, Aug 26, 2014 at 10:40:14AM -0400, Jack Ryan wrote:
> apt-transport-tor should use a separate tor circuit for each line in
> sources.list. Otherwise it may be possible for exit nodes to
> fingerprint systems based on the set of sources.lists lines they use.

So, the default is now to use a different "password" for each host while
connecting to Tors SOCKS proxy causing it to use a new circuit for each
host.

That isn't exactly what was requested as you can and maybe have multiple
lines refering to the same host (like getting indexes for stable and
unstable), but it is close and doing it for each line isn't really
possible to do in the apt architecture as very different layers are
involved here where concepts like "line in a config file" do not make
much sense and things like having multiple connections to the same host
is actively prevented (which would be required for per-line).


So, what we do now is the best we can do – doing more needs user input
if that is still a concern picking multiple (different) mirrors and/or
onion services as sources. Closing as done hence.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: