Unwanted private key revocation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse |
Expired
|
Medium
|
|||
seahorse (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: seahorse
When double-clicking on a revocation certificate of a private key (saved to disk in case the private key is not save anymore / one forgets the key's password), seahorse will automatically revoke that private key without first asking: Are you sure.
I today accidentially revoked my main PGP key that way. This should not happen. Seahorse should as first!
Steps to reproduce:
1) Create a new gpg key. (Lets say it's AABBCCDD)
2) gpg --gen-revoke AABBCCDD
3) copy the revocation certificate to a text file (revk_cert_
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: A revocation certificate should follow
foObArfOofoObAr
foObArfOofoObAr
=FooBa
-----END PGP PUBLIC KEY BLOCK-----
4) Have seahorse-plugins installed
5) Accidentially double-click on revk_cert_
6) Your key is gone!
This should not happen. Between 5) and 6) there should be a confirmation dialog.
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 11 13:50:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/seahorse
Package: seahorse 2.28.0-0ubuntu1
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: seahorse
Uname: Linux 2.6.31-13-generic x86_64
Changed in seahorse (Ubuntu): | |
status: | New → Triaged |
Changed in seahorse: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in seahorse: | |
status: | Confirmed → Expired |
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME)