Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #26359
Closed
Open
Created Jun 12, 2018 by Trac@tracbot

DoS and timed attacks via unencrypted network time protocols

If a device relies on NTP (or any other unencrypted network time protocol), ISP or other party in the middle can manipulate unencrypted packages to set wrong time. Tor relies on correct time, so ISP can deny Tor usage any time it wants to. Moreover, attacker controlling the ISP (government or hackers compromising ISP's server) can manipulate time on tor-using device, assisting attacks that involve wrong time.

Embedded systems like routers have no real-time clock hardware and need to set time via network. PCs are often configured to synchronize time via NTP.

Tor should have other way to set the time it needs. It could set time from directory servers and known relays.

Trac:
Username: time_attacker

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