> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Axel Heider > > some time ago I got this response from Eric Perlin from > Microsoft about their PC/SC implementation: > > > This is no work for the driver. This needs to be handled > > by the app. I recommend a little layer on top of > > SCardTransmit to hide the pecularities of T=0 (vs T=1). > > I think the the MUSCLE implementation should > be compatible to this, too. I agree. I think one goal of MUSCLE is to help hackers to port their Windows applications in new environments (like Linux). The main page of MUSLCE says ("PC/SC compliant resource manager"), and I think we should be compliant with the other 99% of PCSC code. At the moment there are some functions which differ from the MS implementation, e.g: SCardListReaders, which requries a context, even if the other implementation accepts NULL context. What do you think, should we change the trivial differencies to ease porting? Vesa Suontama <[EMAIL PROTECTED]> Tel: +358-40-700 0131 Fax: +358-9-8565 7151 SSH Communications Security Corp Fredrikinkatu 42 http://www.ssh.com FIN-00100 Helsinki, Finland *************************************************************** 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 ***************************************************************
