Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #17716

Closed (moved)
(moved)
Open
Created Nov 28, 2015 by teor@teor

Do clients need to do authority clock checks?

The current code in #4483 (moved) tracks if a client has done a clock check with an authority.

But it doesn't do anything with that information at the moment:

  • making clients wait to contact an authority during bootstrap negates the point of fallback directories (#15775 (moved))
  • making clients continue to contact authorities after bootstrapping risks an inadvertent DoS on the authorities.

How important are client clock checks? Do we need to launch a connection every N hours / days simply to check our clock with an authority? Is it worth the extra load on the authorities? Do we trust the clocks on fallback directories?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking