Delivery-Date: Thu, 31 Jul 2014 14:12:26 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 7F4CA1E0BAF;
	Thu, 31 Jul 2014 14:12:19 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 24A1A30AB1;
	Thu, 31 Jul 2014 18:12:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E798A30A4C
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:12:11 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 5UmbXlFbjyUJ for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 18:12:11 +0000 (UTC)
Received: from khazad-dum.seul.org (khazad-dum.csail.mit.edu [128.31.0.47])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "moria.seul.org", Issuer "moria.seul.org" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id C2D0030844
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:12:11 +0000 (UTC)
Received: by khazad-dum.seul.org (Postfix, from userid 501)
 id 3F1FE1E0BAF; Thu, 31 Jul 2014 14:12:09 -0400 (EDT)
Date: Thu, 31 Jul 2014 14:12:09 -0400
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20140731181209.GD8819@moria.seul.org>
References: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
 <20140731195834.7af66635@meilong>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20140731195834.7af66635@meilong>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [tor-talk] Why make bad-relays a closed mailing list?
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Thu, Jul 31, 2014 at 07:58:34PM +0200, =D6yvind Saether wrote:
> Too bad "ContactInfo email_address" in torrc isn't "ContactInfo
> email_address gpgkey" or alternatively =

> =

> ContactEmail x@y
> ContactKey numbers

Hm? ContactInfo is just a string. You can set it however you like.

Here's the stanza in the torrc file:

## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>

> There is currenctly no safe way to be contacted by the Tor gang and
> this is a problem with your idea.

Another piece of the problem is that we don't enforce any particular
info in the ContactInfo line (or even that you set one at all). I guess
we could send a challenge to the email address, and demand a reply,
and otherwise set a cap on the capacity that the network will assign you.
Seems like that would be another barrier to our volunteer relay operators,
but maybe for exit relays it's worth it.

--Roger

-- =

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

