Delivery-Date: Mon, 27 Apr 2015 20:43:18 -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 5641B1E0C6D
	for <archiver@seul.org>; Mon, 27 Apr 2015 20:43:16 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id F286D347D6;
	Tue, 28 Apr 2015 00:43:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2033C33EEA
 for <tor-talk@lists.torproject.org>; Tue, 28 Apr 2015 00:43:08 +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 yLW-_PJvC8az for <tor-talk@lists.torproject.org>;
 Tue, 28 Apr 2015 00:43:08 +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 E15FC32BF6
 for <tor-talk@lists.torproject.org>; Tue, 28 Apr 2015 00:43:07 +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 9171240C64;
 Mon, 27 Apr 2015 17:43:04 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: phw)
 with ESMTPSA id E39F123C42
Date: Mon, 27 Apr 2015 20:43:02 -0400
From: Philipp Winter <phw@nymity.ch>
To: nusenu <nusenu@openmailbox.org>
Message-ID: <20150428004302.GB25334@nymity.ch>
Mail-Followup-To: nusenu <nusenu@openmailbox.org>,
 tor-talk@lists.torproject.org
References: <223eaa337204f5f94241636062f9a9e4.webmail@localhost>
 <20150423040805.GA7800@moria.seul.org>
 <20150423043420.GA15244@nymity.ch>
 <55394871.4010205@openmailbox.org>
 <20150424024723.GC6723@nymity.ch>
 <553CC9AC.9080402@openmailbox.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <553CC9AC.9080402@openmailbox.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
Cc: tor-talk@lists.torproject.org
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 Sun, Apr 26, 2015 at 11:19:08AM +0000, nusenu wrote:
> > On Thu, Apr 23, 2015 at 07:30:57PM +0000, nusenu wrote:
> >>> 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>
> >> 
> >> I compared your list (71 FPs) with my list (55 FPs) from
> >> 2015-04-05 [1], we have an overlap of (only) 30 relays. An
> >> overlap of around ~50 would be better.
> > 
> > Yes, I remember your list.  Thanks a lot for sharing it, it's
> > really helpful!
> > 
> > The relays that are in your, but not in my list indeed look quite 
> > similar to the rest.  They don't have a BadExit flag because nobody
> > has caught them doing something nasty yet.
> 
> So you do not think that they are controlled by the same (malicious)
> entity? (even though some declare their MyFamily accordingly*)

I'm not sure, unfortunately.

> Or is the requirement to flag them as badexit to catch them red handed?

We don't really have any requirements.  Every case is different and
judged individually.

> The case that one took over legit relays is unlikely since many are
> rather 'fresh' ones.

Maybe somebody started a Tor relay after breaking into them?

> Or: Are they still on the network so we can see what they are after? ;)
> (rather hard given the amount of potential targets)
> 
> Did you (or anyone else?) try to reach out to them via their ISP(s)?

Not yet, but I hope to get to it later today.  It's certainly odd that
all these relays were in only a few data centers.

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

