After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741840 - Inconsistent use of terminology, ctd: OpenPGP, PGP, GnuPG
Inconsistent use of terminology, ctd: OpenPGP, PGP, GnuPG
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
3.14.x
Other Linux
: Normal minor
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2014-12-21 18:05 UTC by Jens Erat
Modified: 2018-08-03 19:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jens Erat 2014-12-21 18:05:02 UTC 
Seahorse has no consistent use regarding the terms OpenPGP, PGP and GnuPG, mixing standards and implementations, and even using the wrong terms.

This question on Ask Ubuntu pretty much describes the confusion created by this, and also includes an example screenshot: http://askubuntu.com/q/564024/167385

I propose following:

- Never use the (trademarked!) term PGP, as I'm pretty sure Seahorse does _not_ interface PGP anywhere.
- Use OpenPGP instead, whenever talking about keys, messages and similar things. OpenPGP is the standard behind PGP and GnuPG, and keys and messages are compatible with other OpenPGP implementations.
- Use GnuPG if actually referring to the implementation used, ie. with error messages and/or explanations what's going on under the hood. It might be reasonable also to use it with the keyring, as the keys actually are stored in GnuPG.

Getting a proper wording, so the user is not confused by the difference between "OpenPGP" and "GnuPG" might not be easy, but it can't get worse than the current one.

In the free software world, we should pay attention on emphasizing the difference between standards and implementations.
Comment 1 Stef Walter 2014-12-22 09:26:00 UTC 
This makes sense. I can help review a patch from you or another party interested in fixing this.
Comment 2 GNOME Infrastructure Team 2018-08-03 19:45:13 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/119.