Feature #5316

Improve OpenPGP documentation

Added by Tails 2013-07-18 07:39:00 . Updated 2019-06-10 14:50:14 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:
End-user documentation

Affected tool:
Deliverable for:


  • Link to the OpenPGP features of Seahorse, for example the key management feature.
  • Link to general introduction to OpenPGP, for example:
  • Mention Enigmail and point to the Thunderbird documentation

“Paperkey reduces the amount of data
to be printed to the bare minimum (secret part of key) and adds
checksums which allow for easier restore of the key when typing it in or
dealing with dirty scans.”


Bug #6568: Mention Seahorse in documentation Confirmed


Feature #9407: Mention OpenPGP best practices Confirmed


Bug #9404: Document how to generate strong OpenPGP keys with Seahorse instead of Claws Mail Resolved


Feature #15174: Mention Enigmail in documentation Rejected


Related issues

Related to Tails - Bug #8999: Claws Mail leaks cleartext of encrypted email to the IMAP server Resolved 2015-03-03
Related to Tails - Feature #9351: Document paperkey Resolved 2015-05-06


#1 Updated by intrigeri 2013-10-04 09:09:07

  • Subject changed from improve openpgp documentation to Improve OpenPGP documentation
  • Starter set to No

#2 Updated by intrigeri 2014-06-21 15:26:28

  • related to Bug #6568: Mention Seahorse in documentation added

#3 Updated by BitingBird 2015-01-28 14:53:32

  • Assignee set to BitingBird
  • Target version set to Tails_1.3.2

#4 Updated by BitingBird 2015-01-31 11:15:22

  • Assignee changed from BitingBird to sajolida
  • QA Check set to Info Needed

I have a doubt… I’m working on a page about Seahorse, but should I put the link to gnupg.org there and consider I’m solving Bug #6568 and this one at the same time? Or does OpenPGP deserve a dedicated page? If so, what else would go in it - we can link to the Seahorse page I’m working on, but we’d better not duplicate information, so 2 links seem not enough content to deserve a page.

#5 Updated by sajolida 2015-02-24 12:26:31

  • Description updated
  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Info Needed to Dev Needed

That’s a bit up to you and you should probably try out things and see how they go.

Maybe I would try first to have a general page about OpenPGP and include Seahorse in there. That page would also be a parent page for the documentation of the OpenPGP Applet. Also check out if we have other OpenPGP related tools. If so, then you could make Bug #6568 a subtask of this one.

Regarding pointing to gnupg.org. Well, we have to do this because it’s upstream but I’m not sure it’s the best documentation about OpenPGP in the world and we should look for other ones (possible translated already). So I would have a look at Security-in-a-Box and the EFF Self-defense Guide first. They must have stuff about explaning the concepts behind OpenPGP and we know they are maintained and translated somehow.

#6 Updated by BitingBird 2015-03-03 00:55:09

  • Description updated

#7 Updated by sajolida 2015-03-03 12:30:31

Note that paperkey will only be added in Tails 1.4 at best, so as of now we won’t be able to close that ticket for Tails 1.3.1. But we can start working on it for sure…

#8 Updated by BitingBird 2015-03-03 13:26:27

  • Target version changed from Tails_1.3.2 to Tails_1.4

We have enough tickets for 1.3.1, it’s ok if this one waits a bit :)

#9 Updated by BitingBird 2015-03-04 10:45:15

I’ll have to mention to configure Claws to save drafts in local folder (either in PGP doc or in Claws doc, not sure).

#10 Updated by sajolida 2015-03-05 15:30:34

  • related to Bug #8999: Claws Mail leaks cleartext of encrypted email to the IMAP server added

#11 Updated by sajolida 2015-03-05 15:30:49

That’s Bug #8999.

#12 Updated by BitingBird 2015-03-05 16:16:46

Well, that’s Bug #8999 to solve it, but I’ll document it here :)

#13 Updated by BitingBird 2015-03-15 18:31:06

  • related to deleted (Bug #6568: Mention Seahorse in documentation)

#14 Updated by intrigeri 2015-03-19 10:01:31

> I’ll have to mention to configure Claws to save drafts in local folder (either in PGP doc or in Claws doc, not sure).

There’s still some hope (?) that someone actually fixes that bug, so maybe hold on a bit before spending time documenting workarounds.

#15 Updated by BitingBird 2015-04-11 14:35:25

  • QA Check deleted (Dev Needed)

#16 Updated by sajolida 2015-05-06 11:12:07

#17 Updated by BitingBird 2015-05-07 04:01:51

  • Target version changed from Tails_1.4 to Tails_1.4.1

#18 Updated by BitingBird 2015-06-29 01:29:46

  • Target version changed from Tails_1.4.1 to Tails_1.5

#19 Updated by BitingBird 2015-08-03 09:28:48

  • Target version changed from Tails_1.5 to Tails_1.6

#20 Updated by BitingBird 2015-08-12 06:19:11

  • Target version changed from Tails_1.6 to Tails_1.7

#21 Updated by BitingBird 2015-11-17 09:58:35

  • Target version changed from Tails_1.7 to 246

#22 Updated by sajolida 2015-11-27 04:45:41

  • Target version changed from 246 to Tails_2.0

#23 Updated by BitingBird 2016-01-27 16:36:04

  • Target version deleted (Tails_2.0)

No date. If somebody wants to steal it, be welcome :)

#24 Updated by Anonymous 2017-06-30 14:07:25

  • Assignee deleted (BitingBird)

Unassigning BitingBird who seems to ask for somebody else to take this over.

#25 Updated by Anonymous 2018-01-16 16:50:10

Anybody interested in taking care of this task?

#26 Updated by sajolida 2018-08-16 19:00:18

  • Description updated

We should mention Enigmail and point to the Thunderbird documentation.

#27 Updated by sajolida 2019-06-10 14:50:14

  • Description updated