Skip to content

GitLab

  • Menu
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 935
    • Issues 935
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • 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
  • #6568
Closed
Open
Created Jan 05, 2014 by sajolida@sajolidaMaintainer

Mention Seahorse in documentation

Originally created by @sajolida on #6568 (Redmine)

At the moment, Seahorse doesn’t have a page in the documentation. We have received reports from users who were thinking that the gpgApplet was the recommended key manager in Tails, which is not the case.

This task implies:

  • Linking upstream documentation.
  • Identifying what is specific to Tails regarding Seahorse.
  • Create a page and linking it from the Encryption & Privacy section, and at least gpgApplet documentation.

Feature Branch: bitingbird:doc/6568-seahorse

Parent Task: #5316 (closed)

Related issues

  • Related to #9404 (closed)
  • Related to #9407 (closed)
  • Related to #15174 (closed)
  • Related to #16221 (closed)
  • Related to #17183 (closed)
Edited May 15, 2020 by sajolida
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking