Delivery-Date: Thu, 30 Apr 2015 15:09:40 -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 4D22D1E103D
	for <archiver@seul.org>; Thu, 30 Apr 2015 15:09:38 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 915273494B;
	Thu, 30 Apr 2015 19:09:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 51A2934943
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 19:09:29 +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 OZD0DCaCQtNu for <tor-talk@lists.torproject.org>;
 Thu, 30 Apr 2015 19:09:29 +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 2D9D53492E
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 19:09:29 +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 9225B4115F
 for <tor-talk@lists.torproject.org>; Thu, 30 Apr 2015 12:09:25 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: phw)
 with ESMTPSA id 3282942961
Date: Thu, 30 Apr 2015 15:09:23 -0400
From: Philipp Winter <phw@nymity.ch>
To: tor-talk@lists.torproject.org
Message-ID: <20150430190923.GI1696@nymity.ch>
Mail-Followup-To: tor-talk@lists.torproject.org
References: <55427070.5050907@georgetown.edu> <55427148.2010000@georgetown.edu>
 <20150430181745.GL10036@mail2.eff.org>
 <CAJOXXmxXYKQtpcWuU_ySO9y4kyGUK6+Tj33XL1bNgu=hqNNwTA@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAJOXXmxXYKQtpcWuU_ySO9y4kyGUK6+Tj33XL1bNgu=hqNNwTA@mail.gmail.com>
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] What is being detected to alert upon?
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 30, 2015 at 02:20:34PM -0400, Frederick Zierold wrote:
> Thanks for replying.  I understand it is a spy vs spy type of situation but
> what do they see currently?  I don't believe they are seeing it by the IP
> addresses (or so they claim).
> 
> Is it something in the handshake the is triggering the alert?

Here's how the Great Firewall does it:
<http://www.cs.kau.se/philwint/gfw/>

And here are some thoughts on TLS handshake signatures that can be used
to fingerprint traffic:
<https://trac.torproject.org/projects/tor/wiki/org/projects/Tor/TLSHistory>

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

