Delivery-Date: Sun, 01 Feb 2015 19:27:35 -0500
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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	URIBL_BLOCKED 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 C2E031E070D
	for <archiver@seul.org>; Sun,  1 Feb 2015 19:27:33 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 97C4133330;
	Mon,  2 Feb 2015 00:27:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 01DDF3328B
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:27:26 +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 behgzLZJFi2P for <tor-talk@lists.torproject.org>;
 Mon,  2 Feb 2015 00:27:25 +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 BE86133285
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:27:22 +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 02D89411A1
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:27:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1422836840; bh=V7bat80CgRTcxveoakTijjMYAznNeW1iduzoBfl7Dgs=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=ZB/6q53eAxFooUP4INoynLwoCi8XFWdsXnn3IR5stnWtTzr+ULBzh+Kqa9DBNAIR1
 QoJLC0Huq6p+CsRbn7EtFO0H3uZWsuhZojGinqTPTQtcbWdT4hWDuA4pTwqcbn9E8Y
 FPGVKrdEwA+wrP0AdZx0QLrKkvSmiLZ8JnqVfU+E=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: when2plus2is5) with ESMTPSA id DA5724015D
MIME-Version: 1.0
Date: Sun, 01 Feb 2015 19:27:19 -0500
From: when2plus2is5@riseup.net
To: tor-talk@lists.torproject.org
In-Reply-To: <CABMkiz5HH5RXp0+QLDmoxOej_5OZrYUheBpHURaEe_S2oXc-nQ@mail.gmail.com>
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
 <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@mail.gmail.com>
 <54CEBA1C.2010206@rawbw.com>
 <CABMkiz5HH5RXp0+QLDmoxOej_5OZrYUheBpHURaEe_S2oXc-nQ@mail.gmail.com>
Message-ID: <32d49600f9487c0d76906f2895b63406@riseup.net>
X-Sender: when2plus2is5@riseup.net
User-Agent: Riseup mail
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] =?utf-8?q?ISP_CenturyLink_Blocking_Tor=3F?=
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This link --> http://lmgtfy.com/?q=centurylink+tor

provided the following piece of info:

[tor-talk] "zeus" virus - Mailing Lists
https://lists.torproject.org/pipermail/tor-talk/2012-August/025327.html


Kind regards,

Matt



On 2015-02-01 18:59, Ben Tasker wrote:
>> This policy document talks about botnet and virus infections, so it
> doesn't seem relevant to OP's friend, because tor and torrent clients 
> are
> neither.
> 
> As it has been known for some infections to establish a connection back 
> to
> their C&C via Tor, it's not inconceivable an ISP (or more likely,
> who-ever's providing their kit) might apply a policy which could
> (deliberately or otherwise) wind up blocking Tor. Whether Tor is 
> malware
> has no real bearing, what matters is whether it's traffic is perceived 
> as
> such by the ISP
> 
> I missed the part about the torrent client, though it sounds like the
> behaviour was slightly different. In either case though, the OP's
> description makes it sound like the external connection dropped in it's
> entirety - for any kind of filtering/blocking that's massive overkill. 
> If
> you were being restricted to a walled garden, outside connectivity 
> might
> appear unavailable unless you were going to a whitelisted IP.
> 
> On my (UK) ISP, a reboot of the router pretty much guarantees a new IP,
> though I have also been with providers where that wasn't the case.
> 
> On Sun, Feb 1, 2015 at 11:43 PM, Yuri <yuri@rawbw.com> wrote:
> 
>> On 02/01/2015 15:24, Ben Tasker wrote:
>> 
>>> Looking at their info page -
>>> http://www.centurylink.com/Pages/AboutUs/Legal/InternetServiceManagement/
>>> -
>>> it seems Century Link run what they call a Protection Program.
>>> 
>>> If they detect (what they consider to be) potentially malicious 
>>> traffic,
>>> the connection gets put in a walled garden to notify the end user.
>>> 
>> 
>> This policy document talks about botnet and virus infections, so it
>> doesn't seem relevant to OP's friend, because tor and torrent clients 
>> are
>> neither.
>> 
>>  As others have said, rebooting the router would likely have acquired 
>> a new
>>> IP, so effectively cancelling a block.
>>> 
>> 
>> Not familiar with CenturyLink, but with Comcast digital cable only
>> rebooting with changed client MAC address would cause an IP change.
>> Otherwise IP is very persistent.
>> 
>> 
>> Yuri
>> 
>> --
>> 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
>> 
> 
> 
> 
> --
> Ben Tasker
> https://www.bentasker.co.uk

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

