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

Re: Default Exit Policy

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Default Exit Policy
From: Roger Dingledine <arma@xxxxxxx>
Date: Mon, 26 May 2008 21:35:20 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 26 May 2008 21:35:29 -0400
In-reply-to: <200805262004.31500.njdube@xxxxxxxxx>
References: <200805222359.35131.njdube@xxxxxxxxx> <20080523110725.GA12432@xxxxxxxxxxxxxxxxxxxxx> <7iwslgoqdq.fsf@xxxxxxxxxxxxxxxxxxxxxxx> <200805262004.31500.njdube@xxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Mon, May 26, 2008 at 08:04:16PM -0500, Nathaniel Dube wrote:
> What about creating a white list/black list for domains in Tor.  That way Tor 
> could allow certain domains (such as google.com) to bypass the default 
> blocks.  This way you would be maintaining security while adding 
> functionality.

Another answer might be
https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitPolicyAddresses

--Roger

References:
- Default Exit Policy
  - From: Nathaniel Dube
- Re: Default Exit Policy
  - From: Ansgar -59cobalt- Wiechers
- Re: Default Exit Policy
  - From: Juliusz Chroboczek
- Re: Default Exit Policy
  - From: Nathaniel Dube

Prev by Author: Re: Backward decryption of Tor traffic after Debian OpenSSL bug disclosure
Next by Author: Re: Fwd: Logistics of International Policy Restrictions (project liberation)
Previous by thread: Re: Default Exit Policy
Next by thread: Re: Default Exit Policy
Index(es):
- Author
- Thread