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 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • 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
  • #6636
Closed
Open
Issue created Feb 03, 2014 by sajolida@sajolidaMaintainer

Improve the ISO verification documentation when done through Tails

Originally created by @sajolida on #6636 (Redmine)

When the documentation on ISO verification was first written, we thought that few people would be doing this process through Tails. Our experience proved that this is actually quite common.

So the documentation could be improved to:

  • Name Tails earlier in the enumeration “Ubuntu, Debian, Tails, etc.”
  • Explain that seahorse-plugins is already installed in Tails.
  • Say that the signing key is already included in Tails.

Related issues

  • Related to #8581 (closed)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking