Hello Iain,

On 14/09/06, Iain MacDonnell <[EMAIL PROTECTED]> wrote:
Now I'm running into an issue when trying to do key-related stuff -
like generate a key-pair, or inject a PKCS#12 file:

~ % pkcs15-init -G rsa/1024 -a 01 -u digitalSignature --so-pin 00000000
--pin 00000000
unable to transmit
unable to transmit APDU
muscle.c:199:: APDU transmit failed: Transmit failed
muscle.c:225:: Error in partial object update: Transmit failed
card.c:513:: returning with: Transmit failed
Failed to generate key: Transmit failed
~ %


In the output from pcscd, I see:

commands.c:1039:() Command too long (260 bytes) for max: 253 bytes
ifdwrapper.c:735:() Card not transacted: 612
winscard.c:1481:() Card not transacted: 0x80100016

This is because the reader does not support TPDU longer than 253 bytes.
If your card is T=1 it should work with the latest pcsc-lite and ccid
driver with the extended APDU support.
If your card is T=0 the extended APDU management must be done by
OpenSC or something else above pcsc-lite.

Yes, the PC/SC standard is limited and does not abstract the
communication protocol.

Bye,

--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to