Delivery-Date: Mon, 22 Dec 2014 16:03:39 -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 2A35C1E0C56;
	Mon, 22 Dec 2014 16:03:38 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 954A232643;
	Mon, 22 Dec 2014 21:03:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 36F6B326CE
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 21:03:30 +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 gsyYGk_nd0Qg for <tor-talk@lists.torproject.org>;
 Mon, 22 Dec 2014 21:03:30 +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 0F906325FD
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 21:03:30 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (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 4B8C840FB5
 for <tor-talk@lists.torproject.org>; Mon, 22 Dec 2014 21:03:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1419282207; bh=AmIq7h1zjdXcUl367dXKX/AugyPXy9xXcQ3QUpRjxjI=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=edA6XtI5hldfIhiA5PMypgKe3ksRA6Jl5qzWna+olJusZ/SdLAeqmdjj6GbA/XNqS
 Eu2/QbTkK9vCz1BgN6SpRrVoxpSjNt6eLeZ7aRXaZyRDJV5M1IDEVsTWHjOZLD1eEu
 ZsQ46NBK4dD1kSX8F6wZ5Xg6kQXyTB/zL/5Jbfy8=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 1908E22261
Message-ID: <54988708.9070806@riseup.net>
Date: Mon, 22 Dec 2014 14:03:04 -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>
In-Reply-To: <20141219221905.GU8030@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/19/2014 03:19 PM, Roger Dingledine wrote:
> The Tor Project has learned that there may be an attempt to incapacitate
> our network in the next few days through the seizure of specialized
> servers in the network called directory authorities. (Directory
> authorities help Tor clients learn the list of relays that make up the
> Tor network.) We are taking steps now to ensure the safety of our users,
> and our system is already built to be redundant so that users maintain
> anonymity even if the network is attacked. Tor remains safe to use.
> 
> https://blog.torproject.org/blog/possible-upcoming-attempts-disable-tor-network
> 
> --Roger

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

