Delivery-Date: Wed, 13 Aug 2014 10:52:09 -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 EAFB61E0DD5;
	Wed, 13 Aug 2014 10:52:07 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 86485308D1;
	Wed, 13 Aug 2014 14:52:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2195E3043B
 for <tor-talk@lists.torproject.org>; Wed, 13 Aug 2014 14:52:01 +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 hcCGd_Vx-uEy for <tor-talk@lists.torproject.org>;
 Wed, 13 Aug 2014 14:52:01 +0000 (UTC)
Received: from sebastianhahn.net (sebastianhahn.net [78.47.18.109])
 by eugeni.torproject.org (Postfix) with ESMTP id E581629EF2
 for <tor-talk@lists.torproject.org>; Wed, 13 Aug 2014 14:52:00 +0000 (UTC)
Received: from shire.fritz.box (pD9E883F8.dip0.t-ipconnect.de
 [217.232.131.248])
 by sebastianhahn.net (Postfix) with ESMTPSA id 0B068EE03AE
 for <tor-talk@lists.torproject.org>; Wed, 13 Aug 2014 16:51:57 +0200 (CEST)
From: Sebastian Hahn <mail@sebastianhahn.net>
Message-Id: <DC9294BD-468D-4DEC-ADC2-6C08EB077742@sebastianhahn.net>
Date: Wed, 13 Aug 2014 16:51:53 +0200
To: tor-talk@lists.torproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Subject: [tor-talk] The Tor network doesn't support Named relays anymore
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="===============6222421704658223094=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============6222421704658223094==
Content-Type: multipart/signed; boundary="Apple-Mail=_8A53148A-79CB-48A1-84C5-758DC9BE11E4"; protocol="application/pgp-signature"; micalg=pgp-sha1


--Apple-Mail=_8A53148A-79CB-48A1-84C5-758DC9BE11E4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear Tor users,

the system for naming relays has been an issue for a long time.
Referring to a relay by the operator-chosen nickname in your Tor
configuration file was never a great idea if you wanted to rely on Tor
using that specific relay. As a band-aid, the Tor directory authorities
implemented a naming system, where one of the flags they gave to relays
which picked a unique nickname, stuck with it for a while, and didn't go
offline for more than half a year, was the "Named" flag. This meant
relying on the dirauths for one more thing, and added complexity for the
dirauth operators.

To rectify the situation, proposal 235[0] was written to evaluate the
possibility of stopping the naming system. The tor-dev thread that
followed lead to a code review to ensure currently running versions of
Tor won't be adversely affected by consensuses without any Named flags.
The result of the analysis is that no such issue could be found, and
we're proceeding with disabling Naming. Please note that this does not
mean you cannot use the "Nickname" field anymore when setting up a
relay.

If you - in your Tor configuration file - refer to any relay by name and
not by identity hash, please change that immediately. Future versions of
Tor will not support using names in the configuration at all.

Please report any issues that you might find, so we can react
accordingly.

Thanks & Cheers
Sebastian

[0]: =
https://gitweb.torproject.org/torspec.git/blob_plain/master:/proposals/235=
-kill-named-flag.txt

--Apple-Mail=_8A53148A-79CB-48A1-84C5-758DC9BE11E4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJT63uKAAoJEKlsb90UDJYb1gQH/jOH+FvLdZPBzLIccllNLHQU
C2/H9qaU6fVMnWDv2Q87pAx+hUSAx47amtFyyzEV/cm3BpLUo3dZDoW5VmUmEoE2
9XdHDMHN4dUrEV0dT0S7nMqB3GZ4n1tSMiM/9tCSVFmlAgb7L4X2nYU3BbXvZ5vW
cDTtdQ4wfpW/VBB0u/aV/oucTwKakX8KNW9LgL8G+QXhxSh1xikF/AS6A4A7xxK2
G1xfzPLjWNFi0Mu6W7hIhuTFzZJYjgHxkVKbsNVoKgL3Flpk2ww7yA+0f6ZErVmc
WCD5UWyoNQ9jAFwEbn3kQ9CXf2jK8CPQ1yF2EZQST93Nmm9C0NzqXbGsJDIYwdI=
=aywg
-----END PGP SIGNATURE-----

--Apple-Mail=_8A53148A-79CB-48A1-84C5-758DC9BE11E4--

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

--===============6222421704658223094==--

