On Wed, Aug 15, 2018 at 12:13 PM, Peter Lebbing
<pe...@digitalbrains.com> wrote:
>> So, perhaps enQsig is using 3DES.
>
> Good find! This sounds plausible.
Created a custom key pair not on a smart card, just for this single
transaction. Result:
>gpg --verbose --decrypt encrypted.asc | head
gpg: armor header: Version: enQsig
gpg: public key is FDE5C6E97DA42AE8
gpg: public key is 92663E7CA68E4EC6
gpg: public key is 9D8C454A43A6D2DE
gpg: encrypted with RSA key, ID 9D8C454A43A6D2DE
gpg: encrypted with RSA key, ID 92663E7CA68E4EC6
gpg: encrypted with 4096-bit RSA key, ID FDE5C6E97DA42AE8, created
2018-09-06
"Felix E. Klee <felix.k...@inka.de>"
gpg: 3DES encrypted data
gpg: Note: sender requested "for-your-eyes-only"
So yes, 3DES!
Fortunately, as can be seen above, with the custom key I was able to
decrypt the message.
Issue solved.
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
