Iain MacDonnell wrote:
The "muscletest" tool that is built with libmusclecard (but not installed anywhere by default - find it in src/.libs) will list objects,
thanks, will have a look.
but I'm not sure how the PKCS#15 files for OpenSC get implemented as MuscleCard objects... is there a 1:1 mapping?
directories get the object id of the dir name, files the object id of the dir+file name. so it somehow emulates a real filesystem.
muscleTool should be able to list objects too... http://muscleapps.alioth.debian.org/
ok, thanks.
Those are plugins for libmusclecard - if libmusclepkcs11 is obsolete, then libmusclecard may be too (if there's no PKCS#11 interface, it's not of much value, IMO).
no, the idea is to merge opensc and muscle, to have one library that can speak to all smart cards. applications can use opensc-pkcs11 then. I think it is better to have one firefox and ssh and pam module that can use opensc-pkcs11 that works with many cards, then to have specialised software for some cards only. easier for users and distributions at least I think.
CFlexPlugin is (was?) for *Crypto*Flex, not CyberFlex.
ah, thanks. I didn't know you could put plugins on cryptoflex cards at all. (it is meant to be loaded on the card, right?) Regards, Andreas _______________________________________________ Muscle mailing list Muscle@lists.musclecard.com http://lists.drizzle.com/mailman/listinfo/muscle
