This was a misunderstanding. Import is possible. The german translation of Kleopatra wrongly indicated an error because it translated "unknown certificates" as "ungültige Zertifikate".

There were two things here:

Works for me now.

On another note. We might also want to reduce the clicks required when certifying a key. The "I have checked the fingerprint" checkbox is out of time. People will check it regardless and we can't force them to do it.

This was a very clear crash that is fixed now. Length was > 76 characters. This caused an improper realloc.

I noticed while looking at Netkey V15 (that signature card) support that we actually didn't have Netkey v2 in the whitelist for supported cards anymore since at least gpg4win 3.0. So I've updated this list accordingly.

@Breach I was analyzing T4056 and wondered where I had seen the error from there before. And I found it in your log.

Ok yeah. I can aim for a Gpg4win for next week, too.

What is the ETA for 2.2.9?

Finally changed it. Especially for keyserver search this was important.

IMO this can be closed. At least the problem for which I intended this ticket is fixed.

I agree that the underlying problem is something else but I also think that if a function can avoid a crash on bad input it should try to do so (or at least assert).

I'm going for Wontfix here. It's just too verbose and I don't really see the point of that additional information.

Well I'm pretty sure the reason is that valuetable_buffer is not inialized in _gpgrt_estream_format. But the resulting behavior confused me. It would not crash. But it would also not print "gpg: Entschlüsselung als fehlgeschlagen angesehen: (null)" It would just print nothing instead of that string.