Hello,

The following link contains the documentation for the next release
of the MuscleCard framework. I'm making it available to get some
feedback. Your feedback is greatly appreciated. Please email me directly
with your thoughts.

http://www.musclecard.com/musclecard-1.0.0-B.pdf

Most importantly, we are concerned with the 32 bit object ID's - will this
limit too many cards ? Could we map object ID's to PKCS-15 objects ?
Should we document how to provide support on Filesystem type cards ?
Can we still keep it simple if we change the Object ID type ?
Could we change Object ID's to strings and still work with
32 bit objects ?

Second, there is no current way to change an Unblock PIN. Should there be
? Should it be a separate function, MSCChangeUnblockPIN. Should it
be part of ChangePIN ? Should ChangePIN map high level pin numbers to
unblock PINs ?

These are crucial. Please respond by next Wednesday if you have thoughts.
The steering team will decide and we will update the documentation.

Best Regards,
Dave

***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to majordomolinuxnet.com with
unsubscribe sclinux
***************************************************************

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]