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 348594 - Leaving signer blank causes encryption to wrong key
Leaving signer blank causes encryption to wrong key
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: libcryptui
git master
Other Linux
: Normal normal
: 1.0.0
Assigned To: Stef Walter
Depends on:
Blocks: 301865
 
 
Reported: 2006-07-25 01:09 UTC by Adam Schreiber
Modified: 2006-08-17 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Schreiber 2006-07-25 01:09:51 UTC 
Selecting none on the libcryptui key dialog results in either encryption to the wrong key or encryption failing.  Selecting a key to sign with doesn't trigger the bug.  This occurs when simply using the EncryptKey interface as well as the libcryptui select recipients dialog.
Comment 1 Stef Walter 2006-07-27 21:47:09 UTC 
Hmmm, I'll look into this. It may have to do with the 'encrypt to self' option.
Comment 2 Adam Schreiber 2006-07-27 22:17:48 UTC 
Thanks.  My procedure was to encrypt to my public key with the applet without a signer. I then select decrypt from the applet and am prompted for the passphrase of the last, alphabetically, of my testing key pairs.  Other times it simply fails.
Comment 3 Stef Walter 2006-08-17 00:55:50 UTC 
Are you sure, could you use libcryptui/tests/cryptui-test-ui and list it's output here? For me when I select no signer I get something like:

RECIPIENT: openpgp:8D4D68687108E308
RECIPIENT: openpgp:FC3108E7F10EA9BA
SIGNER: (null)
Comment 4 Adam Schreiber 2006-08-17 01:07:23 UTC 
(lt-cryptui-test-ui:22049): Gtk-CRITICAL **: gtk_tree_row_reference_get_path: assertion `reference != NULL' failed
RECIPIENT: openpgp:A1F8228111102E54
RECIPIENT: openpgp:8D4D68687108E308
SIGNER: (null)

I tested and can't seem to replicate the bug with the applet or gedit at the moment.  I'll close this and chalk it up to collatoral damage :)