seahorse-tool uses wrong key to encrypt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse-nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have several RSA keys in Seahorse. When I use seahorse-tool ('seahorse-tool -e FILE' or encrypt a file via nautilus) to encrypt a file, the file is always encrypted with the first key, no matter what key I selected.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: seahorse-nautilus 3.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 16 14:25:54 2014
InstallationDate: Installed on 2013-10-26 (263 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: seahorse-nautilus
UpgradeStatus: Upgraded to trusty on 2014-04-30 (76 days ago)
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. 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.
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->
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.