Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 829
    • Issues 829
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #40642
Closed
Open
Issue created Sep 27, 2021 by Duncan@duncan✏Developer

Parse private keys for V3 onion services when included in links

Onionshare 2.4 has just been released, and has switched from using HTTP auth to V3 private keys. As such, users must manually enter the private key in the V3 auth wingpanel in order to view a protected file:

qbert2

As per n8fr8's suggestion, it would be great it Tor Browser would support the parsing of keys placed directly in the link instead, e.g.

http://oy5oaslxxzwib7fsjaiz5mjeyg3ziwdmiyeotpjw6etxi722pn7pqsyd.onion?key=K3N3N3U3BURJW46HZEZV2LZHBPKEFAGVN6DPC7TY6FHWXT7RLRAQ

Thereby pre-filling or silently completing the V3 auth wingpanel entirely.

(Unless there's a good reason why we shouldn't do this @sysrqb/@richard?)

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