Hello, On Mon, Apr 23, 2012 at 21:52, Michael StJohns <[email protected]> wrote:
>>Yes, it is open source and adheres to JavaCard standards and is >>usable(/portable) to different cards, even different javacard >>revisions, but the *interface* it implements is >>proprietary/legacy/non-standard, meaning that it is built 1:1 for >>*-muscle* only. Thus proprietary for what its worth. > > OK - we have a slightly different view of what "proprietary" means in this > instance. For me "proprietary" is "owned by an organization that may change > the interfaces at any time, even if information about the information is > other wise public" E.g. Microsoft and the various Windows APIs. I do understand your point of being non-proprietary, even though I tend to arbitrarily tag and name things the way I see them through my pink/yellow sunglasses 8-) > > I thought of starting from that base of code and re-writing the object > support to incorporate things like the javacard object collection. Just > haven't gotten around to it. This is a new term for me: what is "javacard object collection"? A joint effort on modernizing/re-creating MuscleApplet might be a good idea. >>-15 as a data format is maybe really not relevant here, but -8 dates >>back to 1995, according to Wikipedia. I don't know what is supposed to >>define 7816-4 support, but IMHO claiming that Muscle supports 7816-4 >>is as good as claiming that telnet supports HTTP because they both do >>TCP/IP. But again, 7816-X is a nice ambiguous pile of things, which >>nicely fits the "three blind men and elephant" story :) > > No - -4 is the APDU model which is pretty much the basis for everything else > we build. Which is exactly the "telnet model" I mentioned above. For me, 7816-4 support means support for some "ISO interindustry" commands other than VERIFY (which is a necessity to enable pinpad support in modern world). Be it GET DATA or SELECT FILE or READ BINARY, at least *something* from 7816-4 that is common in the field, with a CLA 0x00. > You could go back and re-write muscle to -8 specs, in fact as additional > functions in the applet without deprecating the others, but to blunt - the -8 > functions are clumsy to use. YMMV. IMHO it doesn't fit on top of muscle interface nor would adding it make any meaningful difference for host-side applications. >>There are some notes on Muscle in OpenSC wiki, which might be of >>interest to anyone interested in either OSS JavaCard applets or Muscle >>in general: >> >>https://www.opensc-project.org/opensc/wiki/MuscleApplet > > > Nice page and matches most of the observations I've got WRT to muscle and its > age. There's also [1] for generic JavaCard pointers. But as you can see I've not updated them for a loong time, so the information might be outdated by now. If you have pointers (like OSS PIV implementation) please let me know or just dump it to the wiki. Martin _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
