[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Simplifying ExoneraTor
On Tue, Jul 7, 2015 at 6:12 PM, Geoff Down <geoffdown@xxxxxxxxxxxx> wrote:
> On Tue, Jul 7, 2015, at 10:12 PM, Zack Weinberg wrote:
>> On Tue, Jul 7, 2015 at 4:50 PM, Geoff Down <geoffdown@xxxxxxxxxxxx>
>>wrote:
>> > What is the relevance of the relay's status at any time other than that
>> > of the incident?
>>
>> That's just the point I'm trying to make. If the relay's status at
>> the (past) time of the incident was different from the relay's status
>> at the (present) time of the investigation, that should be immediately
>> obvious when you look at its page; it should not be a thing buried in
>> a details screen.
>
> But Exonerator at present (and as proposed) requires a datestamp to
> produce any output at all. An investigator will input the datestamp of
> the incident.
I may have gotten this project mixed up with the one that is replacing
Atlas/Onionoo, for which a "dashboard" showing the relay's status at
the present time is the entry point. Still, I think that an
investigator might indeed want to know whether the behavior of the
relay is different now than it was at the time of the incident. For
instance, there would be no point to complaining about exit traffic
emanating from a relay that *was* an exit, but isn't anymore. And a
relay that was only an exit for a brief window of time, that happens
to coincide with an incident, should be suspected to have been hacked.
zw
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays