Delivery-Date: Mon, 06 Oct 2014 05:27: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=-3.2 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_RHS_DOB 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 5B9E91E0A95;
	Mon,  6 Oct 2014 05:27:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id AE140302DA;
	Mon,  6 Oct 2014 09:27:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 80E8F2FF5D
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 09:27:26 +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 7zT1AoXnUGIf for <tor-talk@lists.torproject.org>;
 Mon,  6 Oct 2014 09:27:26 +0000 (UTC)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com
 [IPv6:2607:f8b0:400c:c03::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5D7B92F416
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 09:27:26 +0000 (UTC)
Received: by mail-vc0-f170.google.com with SMTP id hy10so2889716vcb.29
 for <tor-talk@lists.torproject.org>; Mon, 06 Oct 2014 02:27:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=6x4DMPalrR0SBW8jT9J79Oq7A0N2nMm/0lxURoOmxtw=;
 b=0a83zn94h+0KR6Eb+TZP6KKvzGvPRpa9ykuKGLiSJNLD21AGLHLk9SMezCsxpgOFKF
 25oPoactzUMHyy4J3jkMipBnsWFk2EIaw2DRZnGbhnW7mbAPFWfZiuPtxXN5UPvMazvn
 iDaCikb5DfWTycn+8cehGWZhONdvlWcmpVcVwnXYSZahV/UShBl/4ThDxn/57nZRZ0Qx
 SKSApFQFjm3qPF/jJOMLJ4VuPcbeeAL+PHksuoyUlrGb8Ny+Q3U+H1mIoDBYjmAnIBNo
 Tpwk2xQFVBf1C4EWcyid1zdPPwPs+mNy9GYwNfyxOzZ/XO6iUps70CZTonZErtv+//0D
 Yx+g==
MIME-Version: 1.0
X-Received: by 10.52.136.235 with SMTP id qd11mr14462969vdb.3.1412587632406;
 Mon, 06 Oct 2014 02:27:12 -0700 (PDT)
Received: by 10.221.64.74 with HTTP; Mon, 6 Oct 2014 02:27:12 -0700 (PDT)
Date: Mon, 6 Oct 2014 05:27:12 -0400
Message-ID: <CAD2Ti2_s+5hPUJs4jkYz61EFJtQL4rJW0msJeZpPB_Yg9WNF3w@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] Tapping/logging for research [was: media]
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, Oct 3, 2014 at 9:18 AM, Lunar <lunar@torproject.org> wrote:
> Derric Atzrott:
>> There are some strong ethical questions in logging all traffic from a
>> relay, but I can't see any other way to get this sort of data.
>
> The answer to the ethical question is simple: this is plain wrong. You
> don't spy on people.

There's a difference between various depths of research you might
conduct and present:
- This week saw b-traffic in n-sessions to google, facebook, tor2web.
- This week there were 25000 unencrypted POP3 sessions, 20 http, 50 ssh, etc.
- This week there were 25000 unencrypted POP3 sessions to yahoo.
- 10000 from user 0000001@yahoo, 10000 from 0000002, 5000 from 0000003.
- 10000 from USER bob@yahoo, 10000 from mary, 5000 from john.
- Hey look, mary's cheating on bob with john.

At conduction, the last three could be a problem for you and users.
At presentation, only the last two.
The sites and ISP already know exit the hits came from so that's
of no issue to users.

There's a spectrum, so you can't just throw out blanket ethic/legal
over all exit research work.

https://www.youtube.com/results?search_query=netflow+analysis
http://www.alexa.com/topsites
http://www.clamav.net/
https://www.bro.org/

Reminds me, I need to buy more splitters...

> But there's also a legal aspect to it: in many jurisdictions, as soon as
> you start looking at the traffic, you become liable for it.

Looking agnostic is one thing, probably more likely to burn your
eyes out than get legal'd for it. Talking/using [with intent] is another
thing. And of course filtering causes problems when filters fail,
endorsement is pointed at you, you look stupid, or promulgate
police states.

http://www.netnanny.com/
-- 
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

