[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
From: Moritz Bartl <moritz@xxxxxxxxxxxxxx>
Date: Sat, 10 Jun 2017 11:39:25 +0200
Authentication-results: mail.headstrong.de (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=headstrong.de
Cc: support@xxxxxxxxxxxxxx
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sat, 10 Jun 2017 05:39:49 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=headstrong.de; h=content-transfer-encoding:content-type:content-type :in-reply-to:mime-version:date:date:message-id:from:from :references:subject:subject:received; s=mail; t=1497087566; x= 1498901967; bh=zbuRkMsC8L9IID0FC3asxdqVbL5VeZ4F9OSDS6Jhvus=; b=a pUnQJ5RBwmu9JDf8I7lb9B7Q4Y2t69b7Zn06M/1juRmWG598tk340Xgnxwoyi9oz g69LKEzTszZ0GziJn5M5sc6Uexd8dAbzjfH2hxN36Mhnrjw8D8iSRuU6z4+e2M62 Q3ctqVs14AABuz4i4lgFNMAiz1fz+xhXJguW9o9Qxs=
In-reply-to: <20170608120050.GB32734@vpn212046.nrl.navy.mil>
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <341f5a8a-107f-083f-6576-aa561e44b4d9@riseup.net> <20170608120050.GB32734@vpn212046.nrl.navy.mil>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

On 08.06.2017 14:00, Paul Syverson wrote:
> circuit. And if all torservers.net relays are properly indicated to be
> from the same family, they will never be selected for both ends of a
> circuit.

Which is sadly not the case. Our MyFamily statements are badly out of
sync. Will fix this next week.

We had to temporarily disable some of our exits due to ongoing
negotiations with the provider.

Thank you nusenu for watching out!

-- 
Moritz Bartl
https://www.torservers.net/
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
  - From: Gareth Llewellyn
- Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
  - From: nusenu

References:
- [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
  - From: nusenu
- Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
  - From: Paul Syverson

Prev by Author: Re: [tor-relays] Exit / Bad Gateway
Next by Author: Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
Previous by thread: Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
Next by thread: Re: [tor-relays] torservers.net: some exits became guards? (deanonymization risk)
Index(es):
- Author
- Thread