Hello, On Dec 14, 2010, at 10:13 AM, Jean-Michel Pouré - GOOZE wrote: > Would it be possible to know the status of the Muscle applet. We would > be interested in testing the muscle applet with a JCOP card. > > What is exactly the home page of the Muscle applet project? > Is it still: http://www.linuxnet.com/musclecard/index.html > > Could you redirect http://www.linuxnet.com/musclecard/index.html > to the actual page. > > Some questions: > 1) Is the Muscle applet compatible with the JCOP specs? You mean JCOP cards? With some exceptions and assumptions, yes. JCOP is a very varying term with varying technical specifications, YMMV. As original MuscleApplet is quite old, the base code should work on very basic JavaCards but you might not get all the features.
> 2) Do vendors provide a JCOP card with Muscle applet included by > default. I don't think so but I've heard that there are vendors who provide any applets pre-loaded if you buy cards/tokens in a stack of 10. But why do that? As a private person or small company, having the ability to manage your cards (including loaded applets) yourself is the main reason to want them. If you want to buy a stash of cards with a pre-defined, pre-implemented interface, there are better options than MuscleApplet (which is not PKCS#15 by the way) > 3) Can the muscle applet be used to generate a card with 4096bit key RSA > crypto? No, existing JavaCards do not support 4096b keys, at least not to my knowledge and not according to public specs. > 4) Is the Muscle applet actively developed and maintained? Depends. I don't know that it is publicly developed at the moment, but the codebase has been used and re-used several times, by Coolkey, by me, I assume by others as well. I made several improvements to the overall MuscleApplet, some of which is described on OpenSC wiki [1], but what is out of sync with OpenSC (especially OpenSC initialization part). Mostly it was removing unused and questionable features, modernizing the applet (removing support for code that could not be used in my circumstances or what is just a burden on a modern PKI card, transforming the API to a more 7816 like etc) and adding code to for features like extended APDU-s and better key management etc. I should not call it MuscleApplet, or MuscleApplet v2 to add more confusion. I can't publish the whole source tree and right now I lack the time and motivation to work out the necessary modification before next year. Some builds have been circulating on the web though (which were installable via the SmartCardWebApplet). [1] http://www.opensc-project.org/opensc/wiki/MuscleApplet -- @MartinPaljak.net +3725156495 _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
