Hello, I want to abstract the libmusclecard API in the following way:
There are a lot (too much) specification for smart card applications, (EMV, GSM, PKCS#15, national standards, CardEdge applet). All have their special way of storing keys, certificates, data, .... To be able to use different plugins with the MuscleCard API these elements should have a common name, e.g. each secret key has a string identifier "MSCSECRETKEY" followed by a number, each certificate "CERTIFICATE" followed by a number. The plugin translates these identifiers in its equivalent, e.g. an ISO File system ID or an object name for the MuscleCard applet. What different kinds of such objects exist? Is there a superset for this? Any ideas how to solve this in a flexible way? Karsten _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
