Delivery-Date: Thu, 31 Jul 2014 15:13:11 -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 A1C0A1E0BC2;
	Thu, 31 Jul 2014 15:13:09 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5360A309C9;
	Thu, 31 Jul 2014 19:13:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1BC17309B7
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:13:03 +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 ZPtmOzpwAbIV for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 19:13:03 +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 F2E83309AF
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:13:02 +0000 (UTC)
Received: by khazad-dum.seul.org (Postfix, from userid 501)
 id 51F221E0BC2; Thu, 31 Jul 2014 15:13:00 -0400 (EDT)
Date: Thu, 31 Jul 2014 15:13:00 -0400
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20140731191300.GE8819@moria.seul.org>
References: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
 <20140731195834.7af66635@meilong>
 <20140731181209.GD8819@moria.seul.org>
 <20140731201807.039740ea@meilong>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20140731201807.039740ea@meilong>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [tor-talk] is torrc a manual page now? que?
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 08:18:07PM +0200, =D6yvind Saether wrote:
> Thank you for this secret information. Please consider adding it to the
> MANUAL PAGE since I've had my torrc since 2008 and it's not got any of
> that classified information in it. =


Well, it certainly isn't meant to be a secret. You should totally check
out the torrc.sample file that comes with the tarball, or (equivalently)
the torrc file that comes with the deb. It has come a long way since
the last time you looked at it. :)

For reference, here is a copy of the torrc.sample file from Tor
0.1.0.1-rc, released March 28 2005:
https://gitweb.torproject.org/tor.git/blob/fddf560254da197b9e4726b6101f358f=
4b68e7af:/src/config/torrc.sample.in

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

> I don't like this. You are saying you must have a e-mail and reply to
> help out. That is a bad thing. A lot of services these days require you
> to give them (and sometimes verify) a mobile phone number and I
> personally don't use any of those services, sometimes I try to sign up
> for such things but end up backing out because they demand too much
> info. I see no reason why having a valid e-mail and using it to reply
> should be a requirement for helping the Tor network.

I agree -- there are some real downsides to requiring working contact
info for relays.

On the other hand, there are some real downsides to having large relays
where we don't know the operators. We know the operators of many of
the large relays in the network, but there are many more where we don't
know them.

And of course, confirming that some email address can receive email is
not the same as knowing the operators.

So much to do,
--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

