Delivery-Date: Fri, 26 Dec 2014 07:05:38 -0500
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.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED 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 AF2141E0518
	for <archiver@seul.org>; Fri, 26 Dec 2014 07:05:36 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 838583293A;
	Fri, 26 Dec 2014 12:05:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5B2843293A
 for <tor-talk@lists.torproject.org>; Fri, 26 Dec 2014 12:05:28 +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 B1rqWmjj-qz6 for <tor-talk@lists.torproject.org>;
 Fri, 26 Dec 2014 12:05:28 +0000 (UTC)
Received: from imta-36.everyone.net (sitemail2.everyone.net [216.200.145.36])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.everyone.net",
 Issuer "DigiCert High Assurance CA-3" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2B5DE2DCA9
 for <tor-talk@lists.torproject.org>; Fri, 26 Dec 2014 12:05:28 +0000 (UTC)
X-Greylist: delayed 7270 seconds by postgrey-1.34 at eugeni;
 Fri, 26 Dec 2014 12:05:28 UTC
Received: from pps.filterd (omta005.sj2.proofpoint.com [127.0.0.1])
 by imta-38.everyone.net (8.14.5/8.14.5) with SMTP id sBQA237o019817
 for <tor-talk@lists.torproject.org>; Fri, 26 Dec 2014 02:04:14 -0800
X-Eon-Dm: dm0224
Received: by dm0224.mta.everyone.net (EON-AUTHRELAY2 - 43967bc3) id
 dm0224.54862387.14bb56
 for <tor-talk@lists.torproject.org>; Fri, 26 Dec 2014 02:04:13 -0800
X-Eon-Sig: AQLefRFUnTKdAfbvmgIAAAAB,2f62da0e29cd1b7465300f916735105b
X-Originating-Ip: 67.150.123.195
Message-ID: <549D3159.5080008@copper.net>
Date: Fri, 26 Dec 2014 02:58:49 -0700
From: Jim <jimmymac@copper.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090812)
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20141219221905.GU8030@moria.seul.org>
 <54988708.9070806@riseup.net> <20141222211839.GF8014@moria.seul.org>
 <54989935.1020307@riseup.net> <5498A00C.70301@enn.lu>
 <5498A643.3070408@riseup.net>
In-Reply-To: <5498A643.3070408@riseup.net>
X-Enigmail-Version: 0.96.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33,
 0.0.0000
 definitions=2014-12-25_06:2014-12-24,2014-12-25,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
 suspectscore=1 phishscore=0
 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1
 engine=7.0.1-1402240000 definitions=main-1412260109
Subject: Re: [tor-talk] Possible upcoming attempts to disable the Tor network
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>

Thomas White wrote:
> Generally some criteria for DirAuths are people who are trusted by the
> community, aren't raided very often/have legal troubles/could be
> legally compromised, people with an extensive understanding of how Tor
> works and people who can secure their systems from attacks. Remember
> every time a dirauth is added or change IP a new tor version must be
> released as they are hardcoded so it isn't a simple process to add a
> new one, not to mention intra-dirauth communication and verification.

I don't know about the intra-dirauth communication, but as far as the
directory authorities being hard coded, would it make sense to put them
in a small configuration file instead?  If for some reason it is deemed
undesirable to allow users to alter that file, there could be a
requirement the file be signed with one or more private keys and have
the corresponding public keys hardcoded into the code.  It would be much
easier and cheaper to distribute a new, small, signed configuration file
than to release and distribute a whole new version of tor.

Jim


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

