Ingo Struck

> But if the command was sc-hsm-tool -r 0 -i 9 -U large.wrap why is P1:8 rather then P1:9"? yeah, sorry -- pasted the wrong try > Does pkcs15-tool show...

> Have you tried using the -force option? Yes, it shows the same error.

Maybe related to https://github.com/CardContact/scsh-scripts/issues/7 > The problem with 4K key is, that all operations are very RAM consuming and the JVM stretches very close to the limit. https://github.com/CardContact/scsh-scripts/issues/7#issuecomment-598672778 However, the...

> Can you try with a different card reader or try using the Smart Card Shell ? I will try that one first because I currently have no other reader...

> We takes special precautions in the Smart Card Shell by writing larger APDUs in junks to an EF first. > That workaround is however not implemented in the OpenSC...

> And the command in question: 80 74 08 93 00 04 4B is only sending 1109 below the limit. Not for the reader in question. The largest block in...

The inline patch below does the job. However 1. the patch itself it is not yet safe (potentially leaks memory when the loop breaks) 2. the logic to check for...

> In regards to https://github.com/OpenSC/OpenSC/issues/2514#issuecomment-1052323600 using 2F10 sounds like a good idea. But it also referred to EF10. Which is correct? The patch above mimics 1:1 what is implemented in...

It seems there was a good reason that @CardContact kind of "replicated" the chunked transport mechanism elsewhere. I tried to use "built in" chaining, like @frankmorgner proposed, but the card...

> could you check the different APDUs that the two variants are sending. I'd like to check if there is maybe a problem with the generic implementation... Yes, I will...