[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Firefox through Tor
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Firefox through Tor
- From: "Eric H. Jung" <eric.jung@xxxxxxxxx>
- Date: Fri, 28 Apr 2006 15:41:53 -0700 (PDT)
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Fri, 28 Apr 2006 18:41:57 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=EwIenu424aeTswjGEsmmnx3wwewJUV0TKeTONaZdiRvBG6YAZi0gzMkxATk58hu9JiGIGUaXR6jSZGUI/QDyQAeoq/e0Ssm9SCdllLKeuJmlhapfIR1IwBX6W6X0x0YIdPnzy3sE0p99F4VWYDFRjLGTLBii8v0yFBnqxaV8BHA= ;
- In-reply-to: <20060428222854.13952.qmail@web37203.mail.mud.yahoo.com>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
I forgot to mention that if a URL doesn't match any patterns defined in
FoxyProxy, FoxyProxy *does not* default to a direct connection.
Instead, it defaults to the whatever proxy (if any) has been defined in
Firefox's Connection Settings.
By defining Tor as the proxy in Firefox's Connection Settings, Tor is
used as a "catch-all" for non-matches.
I'll shortly be adding blacklist capability to FoxyProxy (it already
has whitelist ability). That, in conjunction, with the above
"catch-all", should provide enough ingredients to come up with some
safe recipe for some of the problems both of you describe, no?
--- "Eric H. Jung" <eric.jung@xxxxxxxxx> wrote:
> Hello Michaels,
>
> I apologize for the delayed reply. Please don't interpret the delay
> as
> a lack of interest--it surely isn't.
>
> Quoting Mike Perry:
> >Just clearing cookies every time there is a switch is not enough if
> >there is an automatic Tor filter in place.
>
> >The problem is that yahoo can custom-generate its links to
> DoubleClick
> >so they encode your email address (dunno if they do do this, but I'm
> >sure some sites and ad parters do). Therefore identifiying
> information
> >is sent independent of the cookie."
>
> I hope you'll both agree there's nothing FoxyProxy can do about this.
> Unless you have a striking relevation which could solve the problem
> programmatically, I'm just going to add this to the FoxyProxy FAQ as
> a
> "be careful" warning in an attempt to educate.
>
> Quoting Mike Perry:
> >See the problem?
>
> Yes, I do now. Thank you.
>
> Quoting Mike Perry:
> >> but if you're asking whether XPCOM allows one to use a proxy
> on/off
> >> based on a page and all its components (images, css files, js
> files), >>the answer is yes.
> >
> >Yes, excellent. That is the property that is needed. If you use that
> >level of control, you are fine."
>
> OK. I will research this further and post my results, especially
> regarding the frames/iframes question.
>
> Quoting Mike Perry:
> >2. Links. Say I want to know who baz@xxxxxxxxx is. I send them a
> mail
> >(possibly spoofed to look like it's from a previous correspondent of
> >theirs) instructing them to click on some link that I control that
> no
> >one else has seen. This can happen inadvertantly or accidentally
> even,
> >I know I've accidentally clicked on an ad banner/stray link here or
> >there.
> >
> >Can you provide some sort of option so that the proxy stays enabled
> >for links clicked from a proxy-enabled page? Would be useful for
> those
> >of us with over-sensitive touchpads :)
>
> This is more difficult, but I've thought of an interesting way to do
> this.
>
> On a related note to this thread, you might find this conversation
> interesting:
> http://s9.invisionfree.com/foxyproxy/index.php?showtopic=10
>
> -Eric
>