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

Closed (moved)
(moved)
Open
Created Jul 25, 2018 by teor@teor

Taint untrusted link authentication keys

We should taint untrusted link auth keys, and then downgrade connections using tainted keys to protocol warnings.

Link auth keys from the following sources are trusted:

  • hard-coded authorities
  • the consensus signed by hard-coded authorities

Link auth keys from the following sources are untrusted:

  • hardcoded fallback dirs, because relay keys change over time
  • our state file (if not confirmed in the consensus), because relay keys change over time
  • onion service descriptors, because they come from untrusted services
  • onion service introduce cells, because they come from untrusted clients

Split off #26924 (moved).

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