Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,013
    • Issues 1,013
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • 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
  • tails
  • tails
  • Issues
  • #6112
Closed
Open
Issue created Jul 18, 2013 by import-from-Redmine@import-from-Redmine

Safer tordate parameters

Originally created by Tails on #6112 (Redmine)

As discussed on tails-dev (4F2FE29F.8040101@lavabit.com, "if we want a long, stable Tor session with a time only handled by tordate (like when htpdate fails), then the only really safe thing to do is to always, no matter what, set the time to fresh-until", which effectively removes "good enough time" check.

  1. implement this
  2. merge into experimental
  3. test in extreme conditions
  4. 4F2FE29F.8040101@lavabit.com also has ideas to improve Tor in these situations, that should be forwarded upstream.

Related issues

  • Related to #5774
  • Related to #5424 (closed)
Edited May 15, 2020 by import-from-Redmine
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking