Delivery-Date: Thu, 23 Apr 2015 00:34: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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY 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 BAD091E0CD4
	for <archiver@seul.org>; Thu, 23 Apr 2015 00:34:32 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7131334F08;
	Thu, 23 Apr 2015 04:34:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0197734EFF
 for <tor-talk@lists.torproject.org>; Thu, 23 Apr 2015 04:34:25 +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 0nMfFsXLew-8 for <tor-talk@lists.torproject.org>;
 Thu, 23 Apr 2015 04:34:24 +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 D255B34EF1
 for <tor-talk@lists.torproject.org>; Thu, 23 Apr 2015 04:34:24 +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 C320341152
 for <tor-talk@lists.torproject.org>; Wed, 22 Apr 2015 21:34:21 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: phw)
 with ESMTPSA id 4E1A443A3F
Date: Thu, 23 Apr 2015 00:34:20 -0400
From: Philipp Winter <phw@nymity.ch>
To: tor-talk@lists.torproject.org
Message-ID: <20150423043420.GA15244@nymity.ch>
Mail-Followup-To: tor-talk@lists.torproject.org
References: <223eaa337204f5f94241636062f9a9e4.webmail@localhost>
 <20150423040805.GA7800@moria.seul.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20150423040805.GA7800@moria.seul.org>
X-PGP-Fpr: B369 E7A2 18FE CEAD EB96  8C73 CF70 89E3 D7FD C0D0
X-Virus-Scanned: clamav-milter 0.98.6 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] SIGAINT email service targeted by 70 bad exit nodes
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 Thu, Apr 23, 2015 at 12:08:05AM -0400, Roger Dingledine wrote:
> On Thu, Apr 23, 2015 at 03:03:57AM -0000, support@sigaint.org wrote:
> > Today we reported 58 bad exit nodes to Philipp. He instantly found 12 more
> > that
> > we had missed, and there may be even more of them. (Thank you, Philipp!)
> 
> Thanks for reporting them. Exciting times we live in.
> 
> Philipp, could you count up what fraction of the network (by capacity)
> these relays were? It is fun to hear big numbers like 70 relays, but at
> least in the past, these attacks that involved many relays have actually
> been a tiny fraction of the network's capacity -- meaning even though
> it seems like a lot of relays, in practice the chance that a Tor user
> will stumble across any of them remains low.

While these relays account for 6% of the total number of exit relays,
they only sum up to 2.7% of exit probability, which is what really
matters.

> I guess that leads to the next question: how long were these relays
> around, and with what patterns did they join the network?

Almost all of them were younger than one month and they seem to have
joined the network in small batches.  I uploaded Onionoo's
JSON-formatted relay descriptors, so everybody can have a look:
<http://www.nymity.ch/badexit/bad_descriptors_2015-04-23.zip>

For example, to find out when all relays joined the network, run:

  grep -h first_seen * | sort

Cheers,
Philipp
-- 
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

