Delivery-Date: Thu, 31 Jul 2014 14:18:34 -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 9D2EC1E0BAF;
	Thu, 31 Jul 2014 14:18:32 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B483A30AB4;
	Thu, 31 Jul 2014 18:18:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2946530A90
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:18:24 +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 XFjDhlL_s_2h for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 18:18:24 +0000 (UTC)
Received: from jessica.everdot.org (unknown [IPv6:2001:470:1f0b:1c12::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id EEE4230862
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:18:23 +0000 (UTC)
Received: from mail.everdot.org (primail.everdot.org [IPv6:2001:470:dc2e:5::2])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by jessica.everdot.org (Postfix) with ESMTPS id B597FFA04DF
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 20:18:20 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.everdot.org (Postfix) with ESMTP id 296CC9122BD2
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 20:18:20 +0200 (CEST)
X-Virus-Scanned: amavisd-new at everdot.org
Received: from mail.everdot.org ([127.0.0.1])
 by localhost (everdot.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id UFqGAK4unQ2B for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 20:18:12 +0200 (CEST)
Received: from meilong (unknown [IPv6:2001:470:dc2e:2:79f9:998d:5cf3:37e9])
 (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.everdot.org (Postfix) with ESMTPSA id A87489122B91
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 20:18:12 +0200 (CEST)
Date: Thu, 31 Jul 2014 20:18:07 +0200
From: =?ISO-8859-1?B?1nl2aW5k?= Saether <oyvinds@everdot.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140731201807.039740ea@meilong>
In-Reply-To: <20140731181209.GD8819@moria.seul.org>
References: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
 <20140731195834.7af66635@meilong>
 <20140731181209.GD8819@moria.seul.org>
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.24; x86_64-pc-linux-gnu)
Mime-Version: 1.0
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: multipart/mixed; boundary="===============0220309220502670659=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============0220309220502670659==
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/Okl3rup1v0ZSTdc8yljXE18"; protocol="application/pgp-signature"

--Sig_/Okl3rup1v0ZSTdc8yljXE18
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

> Hm? ContactInfo is just a string. You can set it however you like.
>=20
> Here's the stanza in the torrc file:
>=20
> ## 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>

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

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

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.

--Sig_/Okl3rup1v0ZSTdc8yljXE18
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlPaiGIACgkQNBSJHnwv/Ko2KQCfawnEYSsUGTz5iPaybfY1tukU
GrwAn0FeYbhO2xu+IGc97ErXydcAog5z
=OLYK
-----END PGP SIGNATURE-----

--Sig_/Okl3rup1v0ZSTdc8yljXE18--

--===============0220309220502670659==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0220309220502670659==--

