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 570706 - wrong key is encrypted to
wrong key is encrypted to
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: libcryptui
git master
Other Linux
: Normal normal
: 2.26.0
Assigned To: Stef Walter
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-02-05 20:24 UTC by Adam Schreiber
Modified: 2018-08-03 19:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test script (602 bytes, text/plain)
2009-02-06 03:50 UTC, Stef Walter 		Details

Description Adam Schreiber 2009-02-05 20:24:24 UTC 
Make sure you have at least 2 valid personal gpg keys
Select or copy some text
In the seahorse-applet select encrypt
Encrypt to your primary key
select decrypt from the applet
you will be prompted for the passphrase for the other key
Comment 1 Stef Walter 2009-02-06 03:50:56 UTC 
Created attachment 128072 [details]
Test script

I can't duplicate this. Does this script exhibit the problem (substituting a valid key id) for you?
Comment 2 Adam Schreiber 2009-02-06 16:25:51 UTC 
That script works.  

I broke out my debugger and found out what's actually happening.  The selected key is being encrypted to properly, but the proper default key isn't being set.  The selection is falling through until "the first secret key" is selected.

The result is that both keys are encrypted to, but because a test key is "first" it's the one the decrypt passphrase is prompted for.

In gconf, my personal key is set as the default key per the preferences dialog.

The reason I haven't uncovered this bug before is that I usually set myself as a signer and the signer is normally chosen first as the default key before gconf is queried.
Comment 3 Stef Walter 2009-03-03 03:10:58 UTC 
I hope it's okay if I leave this in your capable hands.
Comment 4 Stef Walter 2011-03-09 16:11:20 UTC 
Adam, is this working now?
Comment 5 Pablo Castellano (IRC: pablog) 2011-04-20 15:30:50 UTC 
I have had this same issue today, however I was using seahorse-plugins 2.30.1 and Adam's script doesn't reproduce it.

Steps to reproduce:
1. Create several pgp keys (I had three)
2. In seahorse-preferences choose "When encrypting, always include myself as a recipient" and choose some "Default Key"
3. Encrypt a file just choosing some recipient different than you.

The result is that now I click on the encrypted file and seahorse-tool asks me for the passphrase, but not the passphrase of my default key.
If it didn't reproduce the behaviour, repeat from step 2 and choose another "Default Key".
Comment 6 GNOME Infrastructure Team 2018-08-03 19:13:36 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/27.