Andreas Jellinghaus wrote: > Hi Johannes, > > I think it would be great to have full opensc support for the > cards. > > In the documentation I didn't read anything about software updates > so not sure what that binary blob is. maybe the card uploads some > the RSA key rather than uses the cards rsa key generation? >
I suspect the documentation to be incomplete regarding initialization. I have "ACOS5 Reference Manual v1.4, 06-2007". Anything else available? The Upload is 1435 bytes, using CLA/INS 80/34 (undocumented) This is before the card gets any key/certificate, so unlikely to be a RSA key. Will have to compare with a second trace. Then it does some smaller writes, using 'UPDATE BINARY', in locations to locations that are also not documented. But this is at least similar to the ATR customizations described in the manual. The rest is rather standard, and also documented (creatings files and directores, activating them) > > for opensc it would be very interesting if the driver would support both > setups: > a) security officer + normal user > b) single user > > also it would be nice if the card can be erased anytime (if you know the > PINs). i.e. don't finalize it (but there could be an option to do that). > Don't know if this is possible. Documentation talks about "Pre-Perso Stage", "Perso Stage" and "User Stage". This would require that the card is functional in the 'Perso Stage' or there is a way back from 'User Stage'. Jo Deisenhofer _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
