Delivery-Date: Fri, 01 Aug 2014 17:43:51 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 063DE1E08C0;
	Fri,  1 Aug 2014 17:43:50 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2D08030C20;
	Fri,  1 Aug 2014 21:43:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 66DB030402
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 21:43:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 XrSrgfiEW0fW for <tor-talk@lists.torproject.org>;
 Fri,  1 Aug 2014 21:43:41 +0000 (UTC)
Received: from khazad-dum.seul.org (khazad-dum.csail.mit.edu [128.31.0.47])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "moria.seul.org", Issuer "moria.seul.org" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 4BB703027B
 for <tor-talk@lists.torproject.org>; Fri,  1 Aug 2014 21:43:41 +0000 (UTC)
Received: by khazad-dum.seul.org (Postfix, from userid 501)
 id A71BB1E08C0; Fri,  1 Aug 2014 17:43:38 -0400 (EDT)
Date: Fri, 1 Aug 2014 17:43:38 -0400
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20140801214338.GG8819@moria.seul.org>
References: <53DC087E.5070104@bitmessage.ch>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <53DC087E.5070104@bitmessage.ch>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [tor-talk] 'relay early' attack logging at the infrastructure
 level?
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 Fri, Aug 01, 2014 at 09:37:02PM +0000, Nusenu wrote:
> > On July 30th, 2014 arma said: It will indeed kill circuits if it 
> > sees an inbound (towards the client) relay_early cell.
> > 
> > It doesn't have to decrypt the stream to see it, because whether a
> >  cell is relay or relay_early is a property of the (per hop) link, 
> > not a property of the (end-to-end) stream.
> 
> Does a patched relay also create a log entry as soon as it "kills" the
> circuit or is logging only happening on tor instances acting as clients?

The patched relay also does a log message, yes.

But the relay can only see its immediate neighbor in the circuit, so it
will only log that. Whether the attacking relay is that (adjacent) one,
or one farther on the circuit, isn't something your relay can learn.

--Roger

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

