Hello,
>> it worked at least !!
>
>
> Good news :).
Yes, I am really glad and want to thank you all here for your patience
and help !
It seems that it takes some time to get into smartcard programming. Do
you happen to know where to get more detailed information about the
APDU, TPDU and how they are build and how they are supposed to work?
>> > In general I aggree with Jean Luc that all the drivers should present
>> > an APDU level interface. But that would mean to change things in PCSC.
>> > musclecard, and other applications that assume that they work at TPDU
>> > level.
>>
>> So should I better use TPDU's conform commands or APDU conform
>> commands for PCSC? For me everything is quite confusing and sometimes
>> even contradictory.
>
>
> If most drivers work like Carlos' by default, you should treat a case 4
> APDU as a case 3 and send the Get response at the application level.
>
> Anybody willing to share their ideas on this?
For me it only seems to be important that all drivers behave the same
way and are close to a well documented standard, because otherwise it is
very time consuming to develop and mantain the code for different
drivers. It is also quite difficult for a newbie to sort out wether the
own code is wrong or the driver just behaves in an unexpected manner.
Regards,
Arno Wilhelm
--
_ __ ___ _ _ _
/_\ _ _ _ _ ___ \ \ / (_) | |_ ___| |_ __
/ _ \| '_| ' \/ _ \ \ \/\/ /| | | ' \/ -_) | ' \
/_/ \_\_| |_||_\___/ \_/\_/ |_|_|_||_\___|_|_|_|_|
tel://+43/512/394545/72
fax://+43/512/394545/20
mail:[EMAIL PROTECTED]
http://www.phion.com
***************************************************************
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 [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************
