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 733032 - GCR has no man page and employs insecure defauts for GPG passphrase caching
GCR has no man page and employs insecure defauts for GPG passphrase caching
Status: RESOLVED FIXED
Product: gcr
Classification: Core
Component: General
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on: 750514
Blocks:
 
 
Reported: 2014-07-10 20:05 UTC by Andreas F. X. Siegert
Modified: 2019-02-22 11:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas F. X. Siegert 2014-07-10 20:05:25 UTC
gnome-keyring has an inadequate man page and employs insecure defaults for GPG passphrase caching
See https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1325833
Comment 1 André Klapper 2014-07-11 08:45:13 UTC
Please elaborate here what "inadequate" exactly means, and what "insecure defaults" mean, and which version this refers to.
Comment 2 Andreas F. X. Siegert 2014-07-11 08:50:41 UTC
inadequate:
gcr-prompter prompts me for my GPG passphrase. I never configured it to do so, so I start looking for its documentation and do not find any at all in the gcr package.

insecure defaults:
Caching a GPG passphrase for the whole session by default is not good security practice.

version:
gcr package  3.10.1-1  as shipped with Ubuntu 14.04
Comment 3 André Klapper 2014-07-11 10:41:18 UTC
gcr-prompter is not in the $PATH anyway so I have doubts that creating a man page would be a useful effort. (I'm not a gnome-keyring dev though to judge.)

> Caching a GPG passphrase for the whole session by default is not good
> security practice.

Who defines a "good security practice" here and with which arguments?
Comment 4 Andreas F. X. Siegert 2014-07-11 11:03:25 UTC
Well, even a README would help that explains what the package is about which could then reference further documentation to help users understand where the appropriate configuration can be found.

I doubt you will find any security professional who would call caching a GPG passphrase for the entire session by default. Especially when it is not obvious where and how this behavior can be changed.
Comment 5 Stef Walter 2016-02-23 09:58:21 UTC
gnome-keyring no longer implements a gpg-agent. The gnupg agent and pinentry have been better integrated with GNOME.

https://mail.gnome.org/archives/distributor-list/2015-August/msg00000.html