Hi,
Maxim Kammerer wrote (28 Jan 2012 21:40:02 GMT) :
> It will download a new consensus after an hour. If htpdate fails,
> that's where Tor stops working.
I'm surprised a Tor client with a clock less than 30 minutes off will
behave that poorly, but well, I'll let anonym, who knows much more
than me on this, think it through and see if there's anything else
clever enough to be worth being told on this topic.
I think we're going to release 0.10.1 with this change anyway: the
htpdate that will ship in it is muuuuuch more robust, and I think we
can reasonably bet the "clock is way off AND htpdate fails" situation
will be rare enough.
> Also, won't other nodes treat another Tor node with clock time
> before their consensus differently?
(Totally shameless mode ON.)
Please pardon my ignorance, just curious: how does a given Tor node
know about the clock time of another Tor node?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| If you must label the absolute, use it's proper name: Temporary.
