Aborting does not result in a general error any more. Testet with 3.1.26

The flag has been implemented in 2.4 but as long as this version has no approval it does not make sense to do anything more. Let's re-open this task if we have a real request for this.

Your quick support solve my problem, I am thanking you :)
Bye bye

I added a remark to the print function. Thanks for the suggestion.

You are right, w.y should be "00039E2C9AEC146C5799651C42691A3E35E291B6BC45FF079DDA3E70E709BF33".

Can you please share the expected result with us? Note that Libgcrypt strips leading zeroes except when it is required to keep the value positive.

if your'e asking me, i'd suggest just let it be fixed going forward unless someone else complains

Thank you for the report.
Fixed in master. Let us consider if it will be backported to 1.10 (or not).

Here's mirroring script that is in place currently:

#!/bin/bash -e

In T5960#168905, @ebo wrote:

Here is an other instance with broken encoding (on 3.1.27.0-beta44):

It's partially resolved, the rest is wontfix at the moment

I pushed your chnages and removed a lot more code.
See: rPabbecc67

works

works in 3.1.27.0-beta44

For Testversion 3.1.27.0-beta44 for "Regenerate key" now the same algorithms as in 3.2.0 are offered for a Yubikey and it is possible to move them to the smart card.
This is fine even for not VSD-compliant keys, as they are marked as such.

Here is an other instance with broken encoding (on 3.1.27.0-beta44):

This has been solved loooong ago.

@jukivili was so kind and does the mirroring now.

Actually this is about improving an error message.

works. Tested on 3.1.26 with AD configured as keyserver.

closing, as the remaining issue is covered by T6093