Public bug reported:
Binary package hint: seahorse
lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
seahorse:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
*** 2.26.1-0ubuntu1 0
500 http://us.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
After reading the GNU Privacy Gaurd manual for wisdom on key expiration,
I found the recommendation to use a never expiring signing key, paired
with an expiring encryption subkey that can then be replaced at will.
This was, of course, quite easy. When I do a gpg --edit-key on my key, I see
the following:
pub 4096R/472EBFF2 created: 2009-05-21 expires: never usage: SC
trust: ultimate validity: ultimate
sub 4096R/C05B2CE2 created: 2009-05-21 expires: 2010-06-21 usage: E
[ultimate] (1). Stephen J. Carpenter <s...@carpanet.net>
However, in seahorse, there is no distinction at all between the signing
key and the encryption key. Specifically I am looking at the properties
of the key in question, looking on the Owner and details tabs.
In fact, as I created the key as an RSA signing key, the use under the "Owner"
tab read:
"Use: Decrypt files and email sent to you"
This was even before the encrypting subkey was created, even though gpg
clearly recognizes the key as a signing key.
** Affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
--
Seahorse doesn't distinguish subkey usage types
https://bugs.launchpad.net/bugs/379172
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
