gpg encryption: --hidden-recipient about gmime

[jstedfast]

git master has already moved 100% to gpgme :)

I just need to figure out an API to allow the hidden recipient thing...

[gauteh]

Jeffrey Stedfast writes on februar 23, 2017 12:40:

git master has already moved 100% to gpgme :) I just need to figure out an API to allow the hidden recipient thing...

ah great!

[jstedfast]

Looks like this idea got shot down on the gnupg-devel list...

[gauteh]

Jeffrey Stedfast writes on mars 22, 2017 17:24:

Looks like this idea got shot down on the gnupg-devel list...

Yeah, too bad - I think this would be a very useful feature. Was '--throw-keyids' also rejected?

[jstedfast]

I think Werner said something about thinking about that one as he could see some uses for that and it wouldn't be as hard to implement.

[gauteh]

Jeffrey Stedfast writes on mars 22, 2017 22:24:

I think Werner said something about thinking about that one as he could see some uses for that and it wouldn't be as hard to implement.

Ok, it should have more or less the same effect. A regular receiver will know anyway that there are a number of hidden keys and that there likely is Bcc receivers.

[muelli]

FWIW: I think the new 1.9.0 release includes a flag:
https://www.gnupg.org/documentation/manuals/gpgme/Encrypting-a-Plaintext.html#Encrypting-a-Plaintext

GPGME_ENCRYPT_THROW_KEYIDS

The GPGME_ENCRYPT_THROW_KEYIDS symbols requests that the identifiers for the decrption keys are not included in the ciphertext. On the receiving side, the use of this flag may slow down the decryption process because all available secret keys must be tried. This flag is only honored for OpenPGP encryption.

[gauteh]

muelli writes on mars 29, 2017 14:55:

FWIW: I think the new 1.9.0 release includes a flag: https://www.gnupg.org/documentation/manuals/gpgme/Encrypting-a-Plaintext.html#Encrypting-a-Plaintext > > GPGME_ENCRYPT_THROW_KEYIDS > > The GPGME_ENCRYPT_THROW_KEYIDS symbols requests that the identifiers for the decrption keys are not included in the ciphertext. On the receiving side, the use of this flag may slow down the decryption process because all available secret keys must be tried. This flag is only honored for OpenPGP encryption. >

Excellent! I would use this flag only for composing e-mails containing Bcc receivers. If it could be specified to the GMime interface that would solve my issue.

[jstedfast]

Implemented :)

[gauteh]

Jeffrey Stedfast writes on mars 29, 2017 15:11:

Implemented :)

Woha! Nice!