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 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #851
Closed
Open
Created Nov 07, 2008 by Karsten Loesing@karsten

Authorities and clients don't mind expiry of v3 certificates

The certificate of ides has expired on 2008-11-07 09:00:50, but the authority continues signing the consensus and clients continue believing in it:

0 unknown, 0 missing key, 6 good, 0 bad, 0 no signature, 4 required

Although dir-spec.txt does not specifically state whether authorities and clients should behave differently, it says:

Authorities MUST generate a new signing key and corresponding certificate before the key expires.

The current behavior should be changed so that a) authorities don't sign the consensus with a known expired signing key, and b) clients should check whether a certificate is still valid when validating a consensus.

Brought to attention by miner.

[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
Time tracking