Decryption fails with 4096bit key on SmartCard
Marcus Ilgner
marcus.ilgner at gmail.com
Tue Sep 22 16:34:13 CEST 2015
On Tue, 22 Sep 2015 at 16:30 Kristian Fiskerstrand <
kristian.fiskerstrand at sumptuouscapital.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 09/22/2015 03:26 PM, Marcus Ilgner wrote:
>
> >
> > So, again, thanks for helping to investigate! I hope we can find a
> > solution to this :)
> >
>
> Not following this thread too closely, but I couldn't see any debug
> output of the actual failed decryption - you likely want to verify
> that it is encrypted to the public key you expect it to and not
> another subkey that currently isn't available on the computer, this
> often happens when correspondents fails to refresh their keyring
> regularly and you update the setup.
>
You're right, of course, but I checked that first. The output of `gpg
--decrypt` is
[...]
gpg: encrypted with 4096-bit RSA key, ID E3AE1976, created 2015-09-18
[...]
which is one of the key ids also reported by `gpg --card-status`.
All the best
Marcus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20150922/c3af5a3b/attachment.html>
More information about the Gnupg-users
mailing list