On Saturday, December 5, 2020 9:20:33 AM EST Nicolas Boullis wrote:
> PIN retry counter : 2 0 3
It looks like you're trying to decrypt a file and your encryption PIN counter
is zero. I wonder why it was giving you the strange error message.
Does signing work?
signature.asc
Description: This is
On Sun, 6 Dec 2020 16:34:40 +0100, Nicolas Boullis wrote:
> Hi,
>
> On Sun, Dec 06, 2020 at 12:37:19PM +0100, Werner Koch wrote:
>>
>> To make sure that this is really the card (or reader), I'd like to ask
>> you to put
>>
>> --8<---cut here---start->8---
>> lo
Hello,
the --verbose options gave me some more unusual information:
gpg: Schlüssel 22EEE0488086...F: Ungültige Eigenbeglaubigung für User-ID "[jpeg
image of size 7915]"
gpg: Schlüssel 22EEE0488086...F/CE7911B7FC04...F: Ungültige
Unterschlüssel-Anbindung
gpg: key 41E7044E1DBA...9: number of dropp
Hi,
On Sun, Dec 06, 2020 at 12:37:19PM +0100, Werner Koch wrote:
>
> To make sure that this is really the card (or reader), I'd like to ask
> you to put
>
> --8<---cut here---start->8---
> log-file /some/path/scd.log
> verbose
> debug cardio
> --8<
On Sat, 5 Dec 2020 15:20, Nicolas Boullis said:
> gpg: public key decryption failed: Hardware problem
> gpg: decryption failed: No secret key
To make sure that this is really the card (or reader), I'd like to ask
you to put
--8<---cut here---start->8---
log-f
On Sun, 6 Dec 2020 12:12, gnupgpacker said:
> How to identify / correct affected keys?
As usual add --verose to the gpg invocation. This might give some more
information.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PGP
Hello,
my attempt to verify all keys with GnuPG-2.2.25 shows this response:
$ gpg --refresh-keys
gpg: 59 Schlüssel werden per hkps://hkps.pool.sks-keyservers.net aktualisiert
gpg: ...
gpg: signature packet: hashed data too long
gpg: read_block: read error: Ungültiges Paket
gpg: Anzahl insgesamt be
