Directory information no longer up-to-date; access blocked?

[c t]

Thank you for your help and interest in my problem. I believe I had
been using the default torrc; at least I had not edited it. Looking at
that file now, the only lines that are not commented out are:

SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost

I also tried removing the torrc file from /Library/Tor/ and re-running
tor, but no luck—still the same four servers and no ciruit building.
Is there any other place that a dirserver would be specified? Let me
know if there is any further information I could provide to shed more
light.

Thanks again!

On 8/3/07, phobos at rootme.org <phobos at rootme.org> wrote:
> On Fri, Aug 03, 2007 at 10:41:16PM -0400, crt2007z at gmail.com wrote 7.8K bytes in 156 lines about:
> I believe the key is:
> Aug 03 21:33:32.350 [Warning] You have used DirServer to specify
> directory authorities in your configuration.  This is potentially
> dangerous: it can make you look different from all other Tor users,
> and hurt your anonymity.  Even if you've specified the same
> authorities as Tor uses by default, the defaults could change in the
> future.  Be sure you know what you're doing.
>
> Why are you specifying dirservers?  If you use the default torrc, or no
> torrc at all (in /Library/Tor/) does Tor work?
>
> --
> Andrew
>