Delivery-Date: Mon, 22 Dec 2014 17:21:14 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	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 732C11E01A1;
	Mon, 22 Dec 2014 17:21:12 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B76CB32481;
	Mon, 22 Dec 2014 22:21:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 80A2C3234D
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 22:21:01 +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 DNq1g9m-bPnN for <tor-talk@lists.torproject.org>;
 Mon, 22 Dec 2014 22:21:01 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 57DCD32341
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 22:21:01 +0000 (UTC)
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id A99A5411EC
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 22:20:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1419286858; bh=2DFVM5fdtra+xq7sUxcXRVQk41ribXobel5K+9uKobs=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=aNZwuX+A1WTmGLGPGNoS/BY52ZLiXI09i1zuRCD5Dlb6az0jqVHlzSN1vAae3OdTC
 KykFnUFoI/0K4Juc5W+yPLJ1dpCo7DPKSZdSCxjJW9ky/TXkSw/4dwTTF5+N2Ert9H
 uqaWkpbyQmUNtT4dj2uvfpUjn+tGz6Uvt3PI5PoM=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id E4C1E4284F
Message-ID: <54989935.1020307@riseup.net>
Date: Mon, 22 Dec 2014 15:20:37 -0700
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
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>
In-Reply-To: <20141222211839.GF8014@moria.seul.org>
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
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>

On 12/22/2014 02:18 PM, Roger Dingledine wrote:
> On Mon, Dec 22, 2014 at 02:03:04PM -0700, Mirimir wrote:
>> In light of recent posts from Thomas White and some node operators, I'm
>> wondering whether "seizure" might be looking more like "compromise".
>> There might be a range of attacks, from DDoSing to rooting, and perhaps
>> even the covert installation of malicious hardware. Or is that too alarmist?
> 
> So far all is quiet on the directory authority front, and no news is
> good news.
> 
> As for Thomas's servers, I should emphasize that Tor exit relays aren't
> the same as Tor directory authorities. There are 1000+ exit relays in
> the Tor network, and it is normal (and safe) for them to come and go for
> all sorts of reasons. He took his relays down himself to be conservative
> while investigating, but currently he's not thinking it has to do with
> law enforcement. When he took them down, the Tor network temporarily
> lost a little bit of exit capacity, but that too is normal.
> 
> There are six thousand plus relays in the Tor network right now, and
> things are happening as usual. There's no indication currently that
> anything in particular has happened recently.
> 
> --Roger

Thanks for clearing that up. Sorry to confuse things. I saw in the list
of trusted authorities at https://news.ycombinator.com/item?id=8774833
that Riseup runs one, and somehow didn't see that Thomas was reporting
on exit relays and mirrors.

I ought to chill, I suppose.
-- 
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

