You guys (and gals) might want to look into using PKCS#15 (ASN.1 encoding on the card). As a whole, it's kind of nasty complicated but you don't need to use everything. This would allow a somewhat "standard" approach to accessing data on the card. It is very flexable (too flexable if you ask me) and can do just about anything you need, including crypto, certificates, raw data, etc. ASN.1 encoding allows it to be pretty tight space-wise too.
PKCS#15 is published on RSA's website. I recommend looking at snacc for doing asn.1 de/encoding. Interfacing with PKCS#11 is made more natural too. Although I don't have a lot of time for this, I would be happy to help out where I can. I have a lot of experience with PKCS#15, ASN.1, and smart cards in general. -- // Chris >We wanted to implement a very abstract architecture so that KDE >applications could use smartcards without having to know the details of them. > In particular, this would be used for storage, SSL certificates, and KDM >login. > *************************************************************** 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 [EMAIL PROTECTED] with unsubscribe sclinux ***************************************************************
