Questions about particular use cases (integrity verification w/o private key, add E flag to primary key, import secp256k1 key)

Shawn K. Quinn skquinn at rushpost.com
Tue Aug 29 15:24:18 CEST 2017


On 08/29/2017 02:14 AM, s7r wrote:
> Hi Phil,
> Thanks - this is indeed _very_ useful for my use case. I don't think the
> second part is a problem since I can particularly request to not set the
> `throw-keyids` option, but let's say metadata becomes a problem at a
> given point and we decide to use this option, can I tell which recipient
> 'should' be able to decrypt a message based only on the encrypted
> message format if the `throw-keyids` option was used?

No, that's the whole point of throw-keyids. All you're supposed to be
able to tell when using that option, is that none of your keys will
decrypt the message, so it's not for you.

-- 
Shawn K. Quinn <skquinn at rushpost.com>
http://www.rantroulette.com
http://www.skqrecordquest.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20170829/93d374f4/attachment.sig>


More information about the Gnupg-users mailing list