old vs new gnupg - encrypting files

[Hauke Laging]

Am Mi 25.07.2012, 12:48:57 schrieb Chris Clifton:
> Forgive me, can you elaborate on 'encrypting the file to the other one and
> your own key' ?

You can give several recipients. The data is encrypted symmetrically (by AES 
e.g.) by a random key. This random key is asymmetrically encrypted to all 
recipients (or even to a passphrase). Thus an additional recipient increases 
the size of the resulting file slightly only.

gpg --recipient 0x12345678 --recipient 0x87654321 --encrypt ./my/file

See --encrypt-to.

This way you can check whether you can decrypt the data yourself at least.

Furthermore it would have been a lot more useful to get the full error message 
of your recipient instead of a simple "cannot".


Hauke
-- 
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20120725/67a20f66/attachment.pgp>