Delivery-Date: Mon, 06 Oct 2014 18:32:17 -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_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	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 F35101E0F2C;
	Mon,  6 Oct 2014 18:32:15 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6887C307EE;
	Mon,  6 Oct 2014 22:32:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EB18530980
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 22:32:03 +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 OgSatqmlFvef for <tor-talk@lists.torproject.org>;
 Mon,  6 Oct 2014 22:32:03 +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 "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id BC5E730777
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 22:32:03 +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 "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id C7204510AD
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 15:32:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1412634720; bh=Wm4kAZMjwikeBIochuLrIldVbgXRZuadf26qh3NHIxc=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=h90FjnTNzPkGkDXHfDM09rBp5j/H8naQo8f8apy6obMVM+0L7OFR/LFMOU0mo6CCa
 XUe38nAaDA+2ltn54H/S2btFat5iM3IcDkpeDmHmCZY1w8eeA+u1LlCK67Ds3iB65s
 LNoYPPGzmxWb6uwQZXE8NPByhqE8knfPSeVDX5ts=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id E934643131
Message-ID: <54331857.1040204@riseup.net>
Date: Mon, 06 Oct 2014 16:31:51 -0600
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <N1-fSah43VDuP@Safe-mail.net>
In-Reply-To: <N1-fSah43VDuP@Safe-mail.net>
X-Virus-Scanned: clamav-milter 0.98.4 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] isp monitoring tor
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 10/06/2014 04:06 PM, garyr22@Safe-mail.net wrote:
> Sure, I understand what you mean. I'm assuming a situation that
> doesn't involve legal issues. This would be illegal surveillance,
> using average resources with your ISP supporting it for some reason.
> I think Tor would be able to handle this type surveillance if used
> correctly.
> 
> I would like to know what their procedure would be outside of
> monitoring ExitNodes. How much effort it would be to examine the
> packets and get any useful information.

Tor is vulnerable to two general sorts of attacks. One involves the use
of malicious relays in various ways to deanonymize circuits. The other
involves the use of traffic analysis to correlate traffic captured at
edges of the Tor network (to users and the websites that they access).

With ISPs, there's the risk that some organization can monitor traffic
on both ends. It's common to characterize such organizations as "global
passive adversaries". However, a single ISP (or a firm owning multiple
ISPs) could do that, if it provides service to both users and websites.
Also, users who access websites in their own nation via Tor are
similarly vulnerable to their government.

> Thanks
> 
> -------- Original Message -------- From: Crypto <crypto@jpunix.net> 
> Apparently from: tor-talk-bounces@lists.torproject.org To:
> tor-talk@lists.torproject.org Subject: Re: [tor-talk] isp monitoring
> tor Date: Mon, 06 Oct 2014 13:58:10 -0500
> 
>> 
>> 
>> On 10/6/2014 1:51 PM, garyr22@Safe-mail.net wrote:
>>> Hi,
>>> 
>>> How difficult would it be for an ISP to monitor your Tor activity
>>> from the modem and determine what sites you visit?
>>> 
>>> I only need to know if it would be very hard, impossible, or very
>>> possible to do. If it's possible what technique would they use?
>>> 
>>> 
>>> Thanks
>>> 
>> 
>> Gee... That's a tough question. How hard is it to catch the flu?
>> How hard is it to get hit by a car? It depends on who your ISP is,
>> what is specified in their TOS, what monitoring equipment is
>> located at the particular node they are connected to, what the
>> courts have authorized them to monitor, how interested they are in
>> investing the time and money in monitoring you, etc.
>> 
>> -- Crypto https://www.digitalocean.com/?refcode=b90b690ca5bb
>> 
>> -- 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
-- 
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

