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

Re: Is exit policy broken?

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Is exit policy broken?
From: Roger Dingledine <arma@xxxxxxx>
Date: Thu, 30 Jun 2005 18:27:47 -0400
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Thu, 30 Jun 2005 18:27:59 -0400
In-reply-to: <20050630194923.318241408FA1@moria.seul.org>
References: <20050630194923.318241408FA1@moria.seul.org>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.9i

On Thu, Jun 30, 2005 at 12:49:12PM -0700, Bob wrote:
> Hi-
>   I have the following statement in my exit policy:
> 
> ExitPolicy reject 66.35.250.0/24
> 
> This is the first line in my exit policy.
> Yet, in my info file, I have several entries showing connections established
> to *.slashdot.org:

Which Tor server is this?

Which version of Tor?

Are you sure it is running with the exit policy you described? That
is, you restarted (or hupped) it after changing the torrc.

Is your DNS server always returning an IP for slashdot.org that's
within the range in your line above, or is it (sometimes) returning some
other IP?

Does this behavior show up for you with earlier versions of Tor too?

Thanks,
--Roger

Follow-Ups:
- RE: Is exit policy broken?
  - From: Bob

References:
- Is exit policy broken?
  - From: Bob

Prev by Author: Tor 0.1.1.1-alpha is out
Next by Author: (FWD) Re: Howto compile Tor on a windows system
Previous by thread: RE: Is exit policy broken?
Next by thread: RE: Is exit policy broken?
Index(es):
- Author
- Thread