Quote from: randomOVDB#2 on July 06, 2012, 07:24 pmGUI alternative is adding "no-throw-keyids" to gpg.conf, correct ?No, the "no-throw-keyid" (or "no-throw-keyids") option is used to disable the "throw-keyid" (or "throw-keyids") option. By default "throw-keyid" is disabled, but if it is added to the gpg.conf then "--no-throw-keyid" can be used on the command line to override it.The entry from the manual (http://www.gnupg.org/documentation/manuals/gnupg/GPG-Esoteric-Options.html) is here:Quote--throw-keyids--no-throw-keyids Do not put the recipient key IDs into encrypted messages. This helps to hide the receivers of the message and is a limited countermeasure against traffic analysis.1 On the receiving side, it may slow down the decryption process because all available secret keys must be tried. --no-throw-keyids disables this option. This option is essentially the same as using --hidden-recipient for all recipients.The footnote says:Quote[1] Using a little social engineering anyone who is able to decrypt the message can check whether one of the other recipients is the one he suspects.Social engineering might be a little more difficult on SR, though, especially when it comes to obtaining the specifics of an order from a buyer or vendor.Quote from: randomOVDB#2 on July 06, 2012, 07:24 pmCan you post "-v" output of the first message (hQIMA/+...) before decrypting. Mine seems a bit poor, lacking your nick.I did, it was this bit:Quotebash-3.2$ gpg -v address.txt.ascgpg: public key is 048FB30Dgpg: public key is D677EF45gpg: using subkey D677EF45 instead of primary key DD7B4576You need a passphrase to unlock the secret key foruser: "Louis Cyphre <lcyphre@tormail.org>"gpg: using subkey D677EF45 instead of primary key DD7B45764096-bit ELG-E key, ID D677EF45, created 2012-06-16 (main key ID DD7B4576)gpg: using subkey 048FB30D instead of primary key 886855CAgpg: encrypted with 4096-bit RSA key, ID 048FB30D, created 2012-05-11   "Guru <Guru@SR>"gpg: encrypted with 4096-bit ELG-E key, ID D677EF45, created 2012-06-16   "Louis Cyphre <lcyphre@tormail.org>"gpg: AES256 encrypted datagpg: original file name='address.txt'bash-3.2$ Note, the "-v" flag can be added to any GPG operation to get more detail of whatever it is doing.Quotegpg: public key is 048FB30Dgpg: public key is D677EF45gpg: encrypted with ELG key, ID D677EF45gpg: using subkey 048FB30D instead of primary key 886855CAgpg: encrypted with 4096-bit RSA key, ID 048FB30D, created 2012-05-11   "Guru <Guru@SR>"gpg: decryption failed: No secret keyThat shows that you've got Guru's key in your public keyring, but not mine. So you can see at least one of the parties a message is encrypted to, even if you can't see the content of the message.If you import my key to your keyring then the output of attempting to decrypt that first cipher block would look similar (deryption would still fail because you don't have the secret key), but GPG would identify both recipients.