[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Scroogle and Tor
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Scroogle and Tor
- From: Gregory Maxwell <gmaxwell@xxxxxxxxx>
- Date: Sun, 13 Feb 2011 14:55:17 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sun, 13 Feb 2011 14:55:27 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=pBrn2SxytLt52ZnD0i8v8DS7o+LHDk8oHISiJ7E8zWE=; b=STfvzFGwvQK73OBOsa6d+6jh20OOxOYlYgE7CJVaF5x91ztZAb9wg12d5TNIN3RWBd d+48Q9WEKZTezIgySKpnZ9CGkSBj9BOYIliv9dJq7gr62le9F3OdUKpCAg45Y6LxFhMk dJKsvUrIosQvix0F2KfLp6YTiAv1AW6zS9rVU=
- 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=WAvA43b46ey0bbbG2U48c8GbkVGrduk3jILdVtH9BDshDHnEzaLh3VZgdpUDdR0sef KIwNKIC61Ck8oZ7/CyDEVmV/plnCNSBeIghnEAUZTAqM5hIMQNgMee+5QwNolXIQMnxw F3ns7ARC5HDp56hzKFG5XIbMniHYwCO+7t52M=
- In-reply-to: <5321.216.60.71.104.1297624196.squirrel@xxxxxxxxxxx>
- References: <5321.216.60.71.104.1297624196.squirrel@xxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On Sun, Feb 13, 2011 at 2:09 PM, <scroogle@xxxxxxxxxxx> wrote:
[snip]
> I'm getting to the point where I'm tempted to offer my two
> exit node lists (yesterday plus today, and previous six days
> plus today) to the public. If I had more confidence in the
> lists currently available to the public, I wouldn't be
> tempted to do this.
You should. The current public exit service is demonstrably incorrect.
Although it's also important to know why it's incorrect.
For example, one reason that the DNSEL is incorrect is a side effect
of that fact that they are tested to see what address they _really_
exit from. Sometimes an exit is placed behind some proxy and the
address that it claims to be is not the address anyone else sees.
Butâ if an exit has a policy so narrow that it can not be tested by
this process then it will not show up in the DNSEL results.
So, e.g. if I ran a scroogle only exit, it wouldn't be in the DNSEL
results. I'm pretty sure this is the wrong failure mode for the
testing process.
Though this issue means that your non-testing based results will also
be incorrect, just in another way.
There may also be other issues with the DNSEL result which I am
unaware of. The daily/weekly cycle part just sounds like the pattern
of nodes hitting their transfer limits and shutting off. Perhaps the
DNSEL is promptly delisting these nodes when there should be a hold-up
because the DNSEL results are cached.
As far as performance goes, you can download a list of nodes which can
reach a particular address at
https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=1.2.3.4
but, these results have the same problem with omitted nodes that I
mentioned.
As far as the annoying requests from tor goes, it would be better to
subject them to a captcha than to block them completely. Then again,
the big reason people use scroogle via tor is, as I understand it, to
avoid the annoying captchas that google often subjects tor exits to...
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/