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 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • #10614
Closed
Open
Created Jan 11, 2014 by Isis Lovecruft@isis

pt-spec.txt describes using `keyid=fingerprint` in torrc `Bridge` lines

dcf pointed out in this comment on legacy/trac#10559 (moved) that pt-spec.txt claims that little-t tor's parsing of Bridge lines was extended to support keyid=fingerprint (where fingerprint is the digest of the bridge's ID key).

Little-t tor does not support this keyid= prefix. I've tested it; see comment 3 and comment 4 on legacy/trac#9449 (moved). Since it wasn't ever implemented, the keyid= prefix to bridge fingerprints should be removed from pt-spec.txt L27.

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