hidden service descriptors quietly rejected when clock skewed
Mar 29 06:47:33.643 [warn] rend_cache_store(): Service descriptor h7dkd7zc7aeplgy4 is too far in the future
When clients publish hidden services but their clock is wrong, the hidden service doesn't work. There might be a log entry explaining this, but perhaps the log entry doesn't say enough? In any case, a log entry may not be enough to let the user know, if he never looks at his logs.
Is there a better way to communicate this to the user, or is there some way we can cope anyway? (E.g. be more forgiving about clock skew wrt hidden service descriptors (easy) or remember our skew based on dirserver timestamps and have Tor "fix" outgoing published timestamps (foolishly hard))
[Automatically added by flyspray2trac: Operating System: All]