Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 970
    • Issues 970
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • 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
  • tails
  • tails
  • Issues
  • #17544
Closed
Open
Issue created Mar 22, 2020 by intrigeri@intrigeriMaintainer

Expert verification instructions encourage users to certify our key publicly

Originally created by @intrigeri on #17544 (Redmine)

   b. To make an exportable certification of the Tails signing
      key and publish it on the public key servers:

          gpg --sign-key A490D0F4D311A4153E2BB7CADBB802B258ACD84F
          gpg --send-keys A490D0F4D311A4153E2BB7CADBB802B258ACD84F

      Doing so allows people who verified
      your key to verify your certification and, as a consequence, build
      more trust in the Tails signing key.

I don’t think that the level of verification documented in the preceding instructions justifies a public certification of our key.
Encouraging users to do so:

  • spreads suboptimal OpenPGP key signing practices
  • makes our key grow larger and larger
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking