Delivery-Date: Mon, 06 Oct 2014 18:06:53 -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,
	FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,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 9669B1E0AEA;
	Mon,  6 Oct 2014 18:06:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 94827307A7;
	Mon,  6 Oct 2014 22:06:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8BF78302DE
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 22:06:42 +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 LcsfwnajuwhB for <tor-talk@lists.torproject.org>;
 Mon,  6 Oct 2014 22:06:42 +0000 (UTC)
Received: from tapuz.safe-mail.net (www.safe-mail.net [212.29.227.230])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 4EF2425099
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 22:06:42 +0000 (UTC)
Received: by tapuz.safe-mail.net with Safe-mail (Exim 4.63)
 (envelope-from <garyr22@Safe-mail.net>) id 1XbGQP-00035Y-W8
 for tor-talk@lists.torproject.org; Mon, 06 Oct 2014 18:06:38 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=N1-0105; d=Safe-mail.net;
 b=dVCacqKgIN55pKK99XXjYgz+kg2Ee2nrIKyoZlWyjgZdYWiXLom9MesWqHFwEOVH
 Z61UyHEUc18pwwSpctNpuFR8jTHQjPNBu5Z0/jKDxEvnm4yVhvzEOcINynOZy3Ju
 CsZDclRBLBrOaBU6Xsk/xgojRUsaibZOoPCZj2A4f7E=;
Received: from pc ([178.32.181.109]) by Safe-mail.net with https
Date: Mon, 6 Oct 2014 18:06:37 -0400
From: garyr22@Safe-mail.net
To: tor-talk@lists.torproject.org
X-SMType: Regular
X-SMRef: N1-fSah43VDuP
Message-Id: <N1-fSah43VDuP@Safe-mail.net>
MIME-Version: 1.0
X-SMSignature: UkwlH/Efz+OmLKqjIrNnFqO8va8s3sNI1KASQdZV5aOdgdldDTSXBOmA/3NJ05H2
 MrDsvmmZB3bdGrFxayha6MAUTPQyu+ukAOaibkWyh75z5yAfxf5r3AczYRG0NhM1
 WPLrdWz6E1dfHAAIfqBxt7kCp835ms6fC/mgAiCwtrQ=
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>

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.


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

