Delivery-Date: Tue, 05 May 2015 16:24:59 -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,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 D0D481E0478
	for <archiver@seul.org>; Tue,  5 May 2015 16:24:57 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E912E34F08;
	Tue,  5 May 2015 20:24:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D21B134EDA
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:24:50 +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 fGohMxn4Rh3M for <tor-talk@lists.torproject.org>;
 Tue,  5 May 2015 20:24:50 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 9ADCB34E69
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 20:24:50 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gno-or-talk-2@m.gmane.org>) id 1YpjOX-0006gI-H1
 for tor-talk@lists.torproject.org; Tue, 05 May 2015 22:24:45 +0200
Received: from ncc-1701-a.tor-exit.network ([188.138.1.229])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Tue, 05 May 2015 22:24:45 +0200
Received: from wgreenhouse by ncc-1701-a.tor-exit.network with local (Gmexim
 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Tue, 05 May 2015 22:24:45 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: tor-talk@lists.torproject.org
From: W. Greenhouse <wgreenhouse@riseup.net>
Date: Tue, 05 May 2015 20:24:36 +0000
Lines: 33
Message-ID: <877fsmai2j.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>
 <20150505200024.8D647E04BF@smtp.hushmail.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ncc-1701-a.tor-exit.network
X-Archive: encrypt
Cancel-Lock: sha1:4im9XdyQ/FMfG6hrTp5zqRv+IjU=
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>

"l.m" <ter.one.leeboi@hush.com> writes:

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

I wouldn't have cared much, actually. I'm not a Tor developer nor a dirauth
operator nor anything else other than a user who has contributed relays
(without ContactInfo, as it happens). I don't think it makes sense to make
ContactInfo compulsory, but groups of relays on the same AS without contact
or family set should at least be provisionally considered to be related.

If the relay operator hadn't responded, the appropriate response in my opinion
(which is not binding on anyone else) would have been
to observe these relays closely in case the research turned out to involve
active attacks on the network which might make it more possible for third parties
to hurt Tor.

Security research unfortunately is still a "Wild West" field and,
without knowing whether they intended it this way or not, it's certainly the case
that the US-CERT research I mentioned made it more dangerous for a time for
anyone to use or host a hidden service (because the radioactive breadcrumbs
were left for anyone to see). I know that a lot of universities want to
contribute to Tor, but they tend to be pretty obvious about it with setting of
families and nicknames.

Most research can be done on testing networks without exposing human users
, and tor even supplies the software to run test networks.
Risky research on human Tor users should require review board approval
at the university at a minimum, just like testing drugs on humans does.
(Actually it's harder than that, because obtaining "informed consent" from all
users to someone else's "research" is not possible in an anonymous network.)

-- 
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

