While performing some tests with the openCryptoki library[1], I noted that this implementations is actively pushing the CKF_SERIAL_SESSION bit into the ->flags field in the client-provided CK_C_INITIALIZE_ARGS struct. This is causing NSS to break when trying to load this as a pkcs11 modul,e as NSS declares this struct to be a const.
I took a quick look at the most current spec and haven't seen anything specifying access to this struct in C_Initialize (although I admit that actively trying to change these flags on the Cryptoki side is probably a bad idea). Is this something that should be explicitly covered by the spec or something that should just be 'common sense'? Thanks, -Klaus [1] - http://sourceforge.net/projects/opencryptoki/ -- Klaus Heinrich Kiwi | [email protected] | http://blog.klauskiwi.com Open Source Security blog : http://www.ratliff.net/blog IBM Linux Technology Center : http://www.ibm.com/linux/ltc ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
