Cannot decrypt file encrypted with enQsig

Felix E. Klee felix.klee at
Mon Sep 17 18:44:46 CEST 2018

On Wed, Aug 15, 2018 at 12:13 PM, Peter Lebbing
<peter at> 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
          "Felix E. Klee <felix.klee at>"
    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.

More information about the Gnupg-users mailing list