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 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
  • #27288
Closed
Open
Created Aug 23, 2018 by Nick Mathewson@nickm🐻Owner

Tor with NSS must not claim to support LinkAuth=1

LinkAuth=1 is the older one that pokes inside the world of TLS master secrets. NSS sensibly doesn't let us do that, and makes us use RFC5705 like sensible people.

We shouldn't claim to support it, though.

I'm making this a separate ticket from the rest of NSS-TLS, though, since once we merge this, Tor clients and servers will stop working with NSS until legacy/trac#27286 (moved) is merged to update the list of required protocols.

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