Ok, I encrypted the file in question on the new server with :
gpg -vvve -r xxx -r YYY -o filename.dat.pgp filename.dat Where xxx is the problematic key and YYY is our key, and I was able to decrypt the file using my private key with no problems. Not sure if that gives us any more info. I can decrypt with our key at least. Thanks, Chris On Wed, Jul 25, 2012 at 1:16 PM, Hauke Laging <mailinglis...@hauke-laging.de > wrote: > 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 >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users