Comments/questions below. At 05:18 AM 4/23/2012, Martin Paljak wrote: >Hello, > >On Fri, Apr 13, 2012 at 22:05, Jean-Michel Pouré - GOOZE ><[email protected]> wrote: >> Le jeudi 12 avril 2012 à 14:33 +0800, [email protected] a écrit : >>> We are using redhat 5.7and gemalto 64k v2c smartcard.Please help us in >>> doing the integration of smartcard with Linux machine.We have tried >>> out by using opensc tool.But after executing 'opensc-tool -n' its >>> showing JavaCard (without supported applet).Means card is not >>> supported. Can you please suggest any other way to integratte this >>> card to linux machine >> >> If you would like a well-supported card, I suggest your try an OpenSC >> supported card, not a Java card. Of course some people really like Java >> cards and opinion differ. > >The reasons to like JavaCard (in theory) is the ability to: >a) run open source code on/in the card as well, not only on the host side >b) being able to replace/choose the underlying card, be it for >performance or capabilities reason or just replacing the card vendor >when in need > >In practice the only common open source applet, MuscleApplet,
There's also "CoolKey" derived from Muscle as well as a few open versions of the PIV II applet. >is far >from perfect for the on-card code, because: >a) it is in practice proprietary I'm not sure how you came to this conclusion. As far as I can tell, it uses no proprietary classes (and I'm not counting the GP and OP classes as proprietary) and I've been able to run it on at least 5 or 6 different cards. (I think its 4 different families including the old e-card stuff). >b) it is not really maintained Its true there is no real formal maintenance in place for this, but as I recall, there is a public repository, and as recently as last year or so a few fixes we're placed there. It's probably more correct to say there is no one formally responsible for such maintenance. Somewhat more annoying is the lack of a release cycle for the supporting C programs and drivers, especially with respect to Windows. Coolkey is somewhat supported on the Mac platform though. And I do have a copy of the version 2 applet which was supposed to replace v1, but doesn't seem to have ever made it to that point. >c) unrelated to fact that it has code in OpenSC to support the card, >it has no resemblance with IOS7816-4/8/15, which OpenSC is tailored >towards. Which makes it an awkward target in OpenSC. It is correct it is not an -8 or -15 emulation applet. It *is* a -4 applet. AIRC, at the time MuscleApplet was written, -8 really hadn't gotten enough traction and -15 wasn't even a gleam in the drafter's eye. >Having a standards-compliant open source applet would be a huge >benefit, both for the ecosystem as well as OpenSC. But developing this >requires quite a lot of different resources (time, money, motivation >etc) and to date noone has shown interest in this. Maybe - but depending on your needs, it may just be simpler to buy -8 and -15 compliant cards. >Martin > >_______________________________________________ >Muscle mailing list >[email protected] >http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
