[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: exit notation stripping
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: exit notation stripping
- From: grarpamp <grarpamp@xxxxxxxxx>
- Date: Tue, 14 Jul 2009 16:00:17 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 14 Jul 2009 16:00:22 -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=IgkYDNWNjzldtM31/tiNHDa26dw+z8MO39+pvgwk7rk=; b=k+XcC6Gb7+1B2HgUhakQ0MyBzdNy/+DCfsWAa5f/JT/lbJuc3/CYQKyPWII9q/rlJY E7BeQ6hkn/Zw5AT5qs13OOyDLpLSbPLpvIWzqnDaMc1AtI82+RiWeIlWwLlr4sbcSXdf /NU0sARqMboqzyr/AzsuvkX6PU3kWFVauJ+ec=
- 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=Ko+l34Ys82liBDpTgd5b4BYCFJBJDCzv/0UaOtyTT0lUk2tG0rQ0QkGWFVz/xXTKNE EbX/fHnCSEn7suuc5dd36fDC5jjF3FsZiURVb4Ctvw3P3efqoDB9BAJzh61rzmyO2gfI Evn6sE1JhsGqYMMTdjdz0VzyGfoRMzDbJCSF8=
- In-reply-to: <200907140634.n6E6YmX6022296@xxxxxxxxxxxxx>
- References: <200907140634.n6E6YmX6022296@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
> >> > This is why Privoxy includes a filter to strip the exit notation from
> >> > the Host header when passing the request through, and why this filter
> >> Note that this will not work for https obviously.
> >Yep. The smarter place to put this logic would be inside Torbutton
> >(or inside something else in Firefox-land).
> >away. There are too many subtle security and anonymity problems with it.
So long as their browser is set to proxy, I'm not seeing a breach?
Just the issues with website interaction covered by Drake.
I quit it, preferring mapaddress, because it didn't work with https.
> >option for allowing .exit, disabled by default, this change would happen
> >faster. That seems to be the best compromise I can see -- keep users
> >safe by default, and let people screw themselves if they really want
> the .exit notation is the best tool we (non-developers) have for zooming
> in on and identifying bad exits.
I think he means optioning out the http[s]://<url>.<fp>.exit you paste in
your location bar... not removing the mapaddress circuit building functionality,
which is a great tool to have.
Though if I'm just hacking about, I'll tack the .exit on as needed.
Then you've got cases where <ip_addr>.exit and <irc|ssh|etc>.exit
are handy too.
Optioning it off wouldn't be a big deal. Mostly because users would view
the website issues as unexpected. And documenting all the caveats
for new users would be hard. Sort of how some apps have basic and
Removing it, not sure, see what other people say.