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
  • #4390

Closed (moved)
(moved)
Open
Created Nov 05, 2011 by George Kadianakis@asn

The rotation of the TLS context can act as a fingerprint for bridges

Censors can monitor the traffic of a suspected bridge every MAX_SSL_KEY_LIFETIME_INTERNAL and see if the TLS certificate has changed.

Normal SSL services don't change certificates every 2 hours.

Maybe we should consider increasing MAX_SSL_KEY_LIFETIME_INTERNAL. Maybe we should consider implementing and documenting it as part of prop179 (#3972 (moved)).

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