Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #6

Closed
Open
Opened Nov 14, 2004 by weasel (Peter Palfrader)@weasel

Confused server clocks can screw up timing

[Moved from bugzilla] Reporter: nickm@alum.mit.edu (Nick Mathewson) Description: Opened: 2003-08-29 20:44

Some users have reported that the mixminion server has a nasty failure mode when a server's clock moves backwards by a large interval. When the server asks "when did we last (do something)", the answer "tomorrow" can cause crashes or weird behavior.

I'm deferring this for a while, because (a) I want to get 0.0.5 put to bed, and (b) the workaround is trivial: keep your clock set right.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#6