We're trying to add cryptographic support to GSM cards. What we're thinking is hacking some cryptographic application so it reads wirelessly its support files from a card inserted in a mobile phone and registered into the network.
At first what we need is to make clear the scope where OpenSC is to be used and
the scope where Musclecard is to be used.
OpenSC reports that it's to be used with "traditional" smartcards with a file
system, and suggests to avoid Java enabled cards, as they don't have a
filesystem. But indeed GSM cards operators here are using are Java cards and do
have a filesystem. Only from Java Card 2.2.2 on a filesystem is excluded (this
means AFAIK that the package javacard.frameworkx is no longer available, am I
right?)
So OpenSC *could* be used with current GSM cards.
Moreover Musclecard reports being available to Java cards, which include
current GSM cards. Does this mean Musclecard don't make use of the filesystem
in any way?
Also, Musclecard implements PKCS #11 where OpenSC implements PKCS #15. What are
the differences from a practical point of view between #11 and #15?
Also, is a cryptoprocessor in the smartcard needed for using also Musclecard
and OpenSC?
Summarizing: Given that we need cryptographic support into a current GSM Java
card, should we go for OpenSC or for Musclecard?
Any ideas, comments or suggestions are welcome.
Cordially, Ismael
--
Ismael Valladolid Torres w. Madrid (SPAIN)
j. [EMAIL PROTECTED]
http://linuxav.blogspot.com/
http://lamediahostia.blogspot.com/ k. DE721AF4
signature.asc
Description: Digital signature
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
