Project

General

Profile

Bug #9404

Feature #5316: Improve OpenPGP documentation

Document how to generate strong OpenPGP keys with Seahorse instead of Claws Mail

Added by emmapeel over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/14/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Email Client

Description

Reported by user, confirmed by me:

If chosen when configuring GPG support for the account, the button 'Generate a new key pair' will generate a 1024 bit DSA
key, without giving any possibility of changing the type of key or the size.


Related issues

Related to Tails - Bug #9422: Consider disabling key management feature of Enigmail Resolved 05/18/2015
Related to Tails - Bug #6568: Mention Seahorse in documentation Confirmed 01/05/2014

History

#1 Updated by BitingBird over 4 years ago

  • QA Check deleted (Dev Needed)

You should check if it has been reported upstream, but we don't really care because the way we recommend to manage keys is with Seahorse.

#2 Updated by intrigeri over 4 years ago

  • Assignee set to emmapeel
  • QA Check set to Info Needed

#3 Updated by emmapeel over 4 years ago

  • Assignee deleted (emmapeel)
  • QA Check deleted (Info Needed)
  • Type of work changed from Code to End-user documentation

Claws Mail 3.11.1 in Jessie is still not allowing you to choose which kind of key to create, but creates 2048 RSA keys.
Not sure I should report more than a feature request upstream, as 2048 RSA is not as bad as 1024 DSA...
Maybe a warning on our Claws mail configuration docs is a good idea, stressing Seahorse use for generating new keys.

#4 Updated by intrigeri over 4 years ago

Thanks for the info.

Maybe a warning on our Claws mail configuration docs is a good idea, stressing Seahorse use for generating new keys.

Agreed, let's not put too much effort into Claws Mail now, given we might be able to switch to Icedove pretty soon.
I'll let BitingBird add this requirement to whatever ticket about Claws Mail / OpenPGP doc, as appropriate :)

#5 Updated by sajolida over 4 years ago

  • Parent task set to #5316

Note that:

  • Seahorse defaults to 2048.
  • We will soon also have the Enigmail key management inteface to do the same thing (it defaults to 4096).

So, I think we should rather work on documenting OpenPGP best practices in one place and explain that Seahorse is the tool for that. That's now #9407.

Making this a subtask of #5316.

Thankfully, BitingBird is already working on documenting Seahorse in #6568, so we're in good hands.

#6 Updated by intrigeri over 4 years ago

  • We will soon also have the Enigmail key management inteface to do the same thing (it defaults to 4096).

(Background info: IIRC there was some disagreement regarding whether we should expose Enigmail's key management interface to users or not. Not sure if we ended up deciding something, or if there's a ticket or something about it in some blueprint.)

#7 Updated by sajolida over 4 years ago

  • Related to Bug #9422: Consider disabling key management feature of Enigmail added

#8 Updated by intrigeri over 4 years ago

  • Subject changed from Claws Mail PGP plugin generates 1024DSA keys. Cannot be changed. to Document how to generate strong OpenPGP keys with Seahorse instead of Claws Mail

#9 Updated by BitingBird over 4 years ago

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

#10 Updated by u almost 4 years ago

  • Assignee set to sajolida
  • Target version set to Tails_2.2

#11 Updated by sajolida almost 4 years ago

  • Status changed from Confirmed to Rejected
  • Assignee deleted (sajolida)
  • Target version deleted (Tails_2.2)

We removed Claws Mail and Enigmail now proposes 4096R by default, so I think this ticket can be closed.

#12 Updated by sajolida almost 4 years ago

  • Status changed from Rejected to Resolved

The original concern was actually solved and not rejected.

Also available in: Atom PDF