Delivery-Date: Tue, 05 May 2015 16:00:49 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 53CF01E0478
	for <archiver@seul.org>; Tue,  5 May 2015 16:00:47 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0833335091;
	Tue,  5 May 2015 20:00:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2823D35082
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:00:28 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uyLiwLePIihv for <tor-talk@lists.torproject.org>;
 Tue,  5 May 2015 20:00:28 +0000 (UTC)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E59833506F
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:00:27 +0000 (UTC)
Received: from smtp1.hushmail.com (localhost [127.0.0.1])
 by smtp1.hushmail.com (Postfix) with SMTP id ACEF7402CE
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:00:24 +0000 (UTC)
Received: from smtp.hushmail.com (w2.hushmail.com [65.39.178.46])
 by smtp1.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:00:24 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 8D647E04BF; Tue,  5 May 2015 20:00:24 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 05 May 2015 16:00:24 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <87bnhyal86.fsf@example.com>
References: <5548D4B4.9040303@rwth-aachen.de>
 <20150505155135.GD7800@moria.seul.org>
 <20150505163624.5D57FE04BF@smtp.hushmail.com>
 <5548F685.2090704@openmailbox.org>
 <20150505170747.61F8BE04BF@smtp.hushmail.com>
 <55490663.3070407@openmailbox.org>
 <20150505182257.6BF60E04DA@smtp.hushmail.com> <87bnhyal86.fsf@example.com> 
Message-Id: <20150505200024.8D647E04BF@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] the privacy of public tor descriptor data
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Wow. You just blew my mind. So anonymity and privacy for users, but
not contributors that make said privacy features possible? By that
reasoning ContactInfo would be mandatory, which it's not. It also
follows that MyFamily would become a high-priority (mandatory) feature
to implement rather than something which is considered for
elimination. I'm curious--how do you intend to prove two relay with
similar subnet and ASN are related? I would be very interested in that
proof.

So regarding users/clients, don't ask, don't tell, and, in fact,
heavily document how they can avoid identification.

Regarding infrastructure operators. If you withhold *non-mandatory*
information you *will* be suspect. Even if you happen to be a
university. I feel so much better now.

x-num of relays registered to a public institution, forced disclosure
follows, that or be seen as a threat
-> relays associated with department
---> relays associated with research 
-----> relays associated with graduate

-and-

if the research isn't approved by tor network as a whole 
-> researcher becomes a target

-which means-

tor research becomes discouraged 
-> bugs, flaws not identified 
---> state intelligence win

I propose you change the documentation, and the code to reflect your
stance. Which to me sounds like bs. The truth is anonymity of tor is
for the good, and bad, no matter how subjective. It's also a matter of
practice that a relay is only be marked bad if you do something bad,
or are incapable of performing relay duties. Otherwise you loose
flags. At not point is it an acceptable to treat a relay group as
suspect for missing non-mandatory data. The spec and design doc says
you're wrong.

Every researcher falls into two categories: those who support the
government and see tor as a possible threat, and those who support
privacy-anonymity advocacy. Singling out relay operators means the
former consider the choice wise, and makes the latter second guess.

It was wrong to push the operator. Engaging in research isn't wrong.
There's a completely valid reason to not want to have this information
available and this specific event is an example. If you allow elicit
drug harbors because you can't prove where they are--how can you
assume a relay may be malicious without gathering evidence. Your
public descriptors give you no right over the operator identity. Deal
with it.

What if the operator of these relays had ignored you? They should
have. You would have gone bonkers wouldn't you.

--leeroy

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

