Feature #5316: Improve OpenPGP documentation

Feature #5316

Improve OpenPGP documentation

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

Status:

Confirmed

Priority:

Low

Assignee:

Category:

Target version:

Start date:

2014-01-05

Due date:

% Done:

63%

Feature Branch:

Type of work:

End-user documentation

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

Link to the OpenPGP features of Seahorse, for example the key management feature.
Link to general introduction to OpenPGP, for example:
- http://www.gnupg.org/gph/en/manual.html
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.”

Subtasks

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

History

#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…