[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Bad exit node: freeMe69

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Bad exit node: freeMe69
From: KT <listclient@xxxxxxxxx>
Date: Thu, 20 Aug 2009 23:10:04 +0100
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Thu, 20 Aug 2009 18:17:21 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=gJUMHq/VgKs0rRkSNuTpJ5VCW00NCOreiBhtq6JK4hU=; b=jNGj6eOo4dB9jsMrm7S8JTM9swj5Q4u25FVaR7iER1U+8FgmctwxN06O0hFjkP/XTC EVzgUhUfMiuYHX4Sc5bPog1CTpNcwEHZqMXOgCASNzPT9d/3RGmSZegSWKo0HUuHpg2B jVobFdNzKtH0zyCvQrySUBEAZBjoWA5qDAXmg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Nr9LVe9CQAJEMVDSFYBVppEnxcGbcYka1LQfe1zoADIOjJcnxGL6lxuSx4j3jL6RgW m7h6LxJ+Kl8lESfMVYVUGKNbJ95QiJsdftky0uN6vZKsFq9dt46r1pWrBe/0Cmu9JkkM jUobmsStS4hCNwfRlgw3Ps13SaTpOG7GqOpRU=
In-reply-to: <5FE0B39E-48A4-4B07-879D-93FFA1C9C6B7@xxxxxxxxx>
References: <4e79549a0908201402n60ef4658y3968e9e66328e618@xxxxxxxxxxxxxx> <5FE0B39E-48A4-4B07-879D-93FFA1C9C6B7@xxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On 8/20/09, Tom Hek <tor@xxxxxxxxx> wrote:
> On Aug 20, 2009, at 23:02 PM, KT wrote:
>
>> Exit node freeMe69 [1] is injecting the following snippet to
>> response body:
>>
>> <script type="text/javascript"
>> src="http://s.tobban.com/solver/cpt.php";></script>
>>
>> [1] http://tinyurl.com/mz9d7e
>
> It's actually injected by it's ISP, Comcast.

Excuse my ignorance...I can imagine it might be injected upstream but
you know this how?

> The IP which s.tobban.com
> resolves to is assigned to Comcast. I don't think the exit node admin
> can't do anything about it.

s.tobban.com resolves to the *IP address of the exit node* which is on Comcast.

regards
KT

Follow-Ups:
- RE: Bad exit node: freeMe69
  - From: downie -

References:
- Bad exit node: freeMe69
  - From: KT
- Re: Bad exit node: freeMe69
  - From: Tom Hek

Prev by Author: Bad exit node: freeMe69
Next by Author: Re: Testing Tor Browser Bundle 1.2.7-dev
Previous by thread: Re: Bad exit node: freeMe69
Next by thread: RE: Bad exit node: freeMe69
Index(es):
- Author
- Thread