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 592956 - Can't revoke subkey
Can't revoke subkey
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
git master
Other Linux
: Normal major
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks: 609024
 
 
Reported: 2009-08-24 21:23 UTC by Andreas Moog
Modified: 2010-02-22 04:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas Moog 2009-08-24 21:23:47 UTC
Forwarded from Launchpad (https://bugs.launchpad.net/bugs/228876)

Steps to reproduce:

1. Select gpg-key -> Properties
2. On Details-Tab choose a subkey
3. Revoke, Superseded - blank comment field. Seahorse gives dialog:
Couldn't revoke subkey
General error

And .xsession-errors shows:
** (seahorse:6771): CRITICAL **: file seahorse-gpgme-key-op.c: line 1759 (rev_subkey_transit): should not be reached
Comment 1 Pablo Castellano (IRC: pablog) 2010-02-20 04:18:13 UTC
This is important for the release. I'll have a look at it tomorrow.
Comment 2 Pablo Castellano (IRC: pablog) 2010-02-20 17:30:52 UTC
Fixed! :)

commit ef5874328c8a3155e8f38be3ec396f9583b9ba1b
Author: Pablo Castellano <pablog@src.gnome.org>
Date:   Sat Feb 20 18:14:34 2010 +0100

    Revoking subkey now works again. Also minor documentation changes.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=592956
Comment 3 Pablo Castellano (IRC: pablog) 2010-02-20 17:31:52 UTC
It is strange. I had never revoked a subkey with seahorse and I wonder if it really worked once in the past. If so, something has changed in the communication with gpg and I could have broken again compatibility with older versions :?
Comment 4 Adam Schreiber 2010-02-20 17:50:03 UTC
Pablo, thanks for taking care of this.  It was on my todo list.  I just tested it and I'm using gpg 1.4.9.  If it also works for 2.x then I think we're ok.  I think I'm going to look at changing the default subkey created to RSA 2048, but that might count as a UI change.
Comment 5 Pablo Castellano (IRC: pablog) 2010-02-20 18:28:18 UTC
(In reply to comment #4)
> Pablo, thanks for taking care of this.  It was on my todo list.  I just tested
> it and I'm using gpg 1.4.9.  If it also works for 2.x then I think we're ok.  I
> think I'm going to look at changing the default subkey created to RSA 2048, but
> that might count as a UI change.

Yes, it works with gpg 1.4.9 and 2.0.12 at least :)
I support changing to create rsa 2048 subkeys by default. Will you ask for the approval?

What about changing configure.in to use by default gnupg2 if it's found? Is it well tested? I have found that sometimes gpg freezes the UI and with gpg2 I didn't get that impression:
106:		AC_PATH_PROGS(GNUPG, [gpg2 gpg], no)
Comment 6 Adam Schreiber 2010-02-21 23:11:43 UTC
Because there are two different kinds of RSA subkey that can be generated -- RSA_SIGN, RSA_ENCRYPT -- this will require more thought.  In the meantime, I have changed the default subkey lengths to DSA_MAX and MAX_LENGTH / 2.  No UI freeze break required.

commit dd47282ec4dfc4d7319004e3ea1810d4667b881c
Author: Adam Schreiber <sadam@gnome.org>
Date:   Sun Feb 21 18:08:57 2010 -0500

    Change default key lengths for subkey generation.
Comment 7 Pablo Castellano (IRC: pablog) 2010-02-22 04:22:31 UTC
In fact, I was wondering if what you did (change something in the UI from the source code) is considered an UI change. :)

But why MAX_LENGTH / 2 ?
Comment 8 Pablo Castellano (IRC: pablog) 2010-02-22 04:34:58 UTC
Okay I have read it in https://bugzilla.gnome.org/show_bug.cgi?id=605497
;)