> Like many encrypted tunnel setups, Tor requires both ends to have similar > date/time. You can easily test this by manually setting to the wrong > time, and watching the Tor fail. > > Tor also checks your local date/time against the consensus status > document, and will warn you if it's off. If it's too far, you won't get > tunnels. > > Connecting to Hidden services , I think, requires that local date/time > be within 60 mins of the service provider. > > Tails has a mechanism to set local time. Whonix has a similar mechanism, > also available in Whonix-Qubes.
I guess I realize that Tor and other networking systems require accurate time, I'm just wondering, protocol-wise, *why*? TCP/IP doesn't care. Is the time rolled into some security hash to prevent replay attacks or something? (If so, that'd be easy to fake.) Or is it for timeout purposes, to give up on a sluggish route (in the case of Tor) and choose another one (or something to that effect)? If so, do you really need second accuracy for that? Just curious as to why there's a need for all this time syncing. JJ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0fde654b3f2726fa60a9fe07b470246e.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.