Even though some time went by since this bug has been filed, I would like to reply, because I had a similar strange experience today when I ported the Seahorse Nautilus plugin to Caja for the Mate desktop. In my opinion it is meant to be rather a feature than a bug. After some hours of trying to understand what the source code does, I found the setting "encrypt-to-self" in the Gsettings under dconf->desktop.gnome.crypto.pgp. If this boolean is checked (what it is by default), the seahorse encryption will add your own key to the list of recipients. So you will always be able to decrypt a file even if you had only selected a foreign public key for encryption. For some reason, the developers of this module decided to use a key for encryption, that you did not select!!! After I unchecked the "encrypt-to-self" feature, the software behaved more predictable.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342696 Title: seahorse-tool uses wrong key to encrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/1342696/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
