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

Closed (moved)
(moved)
Open
Created Jan 25, 2017 by Georg Koppen@gk

Update gpg verification instructions for Linux users on our verifying signatures page

Doing a

gpg --verify Downloads/tor-browser-linux64-6.5_en-US.tar.xz{.asc*,}

seems to break under some circumstances for Linux users yet we recommend something like that on our website where we explain how to verify the signatures of freshly downloaded Tor Browser bundles.

It seems to me doing something like

gpg --verify tor-browser-linux64-6.5_en-US.tar.xz.asc tor-browser-linux64-6.5_en-US.tar.xz

is a saner approach.

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