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

Re: BOGUS AUTHORITY ALERT: interesting cached-status/1A0999C05AE2B9A3CF474077F06060E91B3A847 file

To: or-talk@xxxxxxxxxxxxx
Subject: Re: BOGUS AUTHORITY ALERT: interesting cached-status/1A0999C05AE2B9A3CF474077F06060E91B3A847 file
From: Peter Palfrader <peter@xxxxxxxxxxxxx>
Date: Tue, 1 Apr 2008 08:25:21 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 01 Apr 2008 02:25:27 -0400
In-reply-to: <200804010451.m314ppp2022402@xxxxxxxxxxxxx>
Mail-followup-to: or-talk@xxxxxxxxxxxxx
References: <200804010451.m314ppp2022402@xxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Mon, 31 Mar 2008, Scott Bennett wrote:

> >Your client or cache probably got the bogus v2 networkstatus by going
> >to one of the caches and asking for "all" v2 networkstatuses. The bogus
> >ones will expire after a while.
> >
>      But is there currently a way that I can, w.r.t. my torrc, "learn" from
> the experience?  I.e., is there a way I can tell it to *reject* any such bogus
> networkstatus documents regarding that "authority" in the future?

How will you know it's bogus?

Calm down, all is fine.  Move on.

References:
- Re: BOGUS AUTHORITY ALERT: interesting cached-status/1A0999C05AE2B9A3CF474077F06060E91B3A847 file
  - From: Scott Bennett

Prev by Author: Re: [OT] mitigating or defeating syntax analysis
Next by Author: Re: Ubuntu apt archives typo, Hardy platform?
Previous by thread: Re: BOGUS AUTHORITY ALERT: interesting cached-status/1A0999C05AE2B9A3CF474077F06060E91B3A847 file
Next by thread: Re: BOGUS AUTHORITY ALERT: interesting cached-status/1A0999C05AE2B9A3CF474077F06060E91B3A847 file
Index(es):
- Author
- Thread