> > so much for now. i don't know what i need to do to support T=0 in a
> > driver. my usb capture shows how the windows driver uses T=1, and i
> > doubt that a character based protocol over usb is usefull.
> > i found that opensc always uses T=0 and modified it to request ANY
> > protocol. what is the meaning of 0xff as return value for active protocol?
>
> 0xFF means Error. Look at pcsclite.h for protocol information.
>
> About T=0/1 - you will have to write this if your token does not do this.
> but if your token does not use T=0, then why write a T=0 stack ? You can
> make a fake ATR for your token, and not use T=0.

i meant 0xff as value in active_proto. the return value is 0, so it's
ok. i guess 0xff means that T=0..7 are allowed ? anyway, now opensc
is speaking T=1. or at least i guess by the pcscd output:
...SCardTransmit: Send Protocol:1

which is what i want.

Thanks, andreas

***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to majordomolinuxnet.com with
unsubscribe sclinux
***************************************************************

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]