OpenSolaris

Printable Version Enter a New Search
Bug ID 6368332
Synopsis libpkcs11 should report that it is v2.20 not v2.11
State 10-Fix Delivered (Fix available in build)
Category:Subcategory solaris-crypto:pkcs11
Keywords ef-other | ef-reviewed
Responsible Engineer Darren Moffat
Reported Against s10u2_04
Duplicate Of
Introduced In
Commit to Fix snv_32
Fixed In snv_32
Release Fixed solaris_nevada(snv_32) , solaris_10u2(s10u2_05) (Bug ID:2133887)
Related Bugs
Submit Date 3-January-2006
Last Update Date 23-January-2006
Description
pkcs11Global.h 	52 #define CRYPTOKI_VERSION_MINOR 11

Should have been updated to "20".  Not doing so causes this code in
$SRC/lib/pkcs11/libpkcs11/common/pkcs11Conf.c

   436 		/*
    437 		 * Warn the administrator that a provider with
    438 		 * a significantly older or newer version of
    439 		 * CRYPTOKI is being used.  It should not cause
    440 		 * problems, but logging a warning makes it easier
    441 		 * to debug later.
    442 		 */
    443 		if ((prov_info.cryptokiVersion.minor <
    444 			CRYPTOKI_VERSION_WARN_MINOR) ||
    445 		    (prov_info.cryptokiVersion.minor >
    446 			CRYPTOKI_VERSION_MINOR)) {
    447 			cryptoerror(LOG_INFO,
    448 			    "libpkcs11: %s CRYPTOKI minor version, %d, may "
    449 			    "not be compatible with minor version %d.",
    450 			    fullpath, prov_info.cryptokiVersion.minor,
    451 			    CRYPTOKI_VERSION_MINOR);
    452 		}

To spew messages for every telnet/rlogin and many ssh connections.



There are two problems here:

	1) That fact that we are advertising libpkcs11 as being v2.11
	when we have plugins we ship that have v2.20 mechs and
	features in them.

	2) The fact that we warn about this at all at LOG_INFO
	this should really just be dropped to LOG_DEBUG since
	the Cryptoki working group is well behaved with respect
	to API compatibility in minor versions - they are even
	more strict than the Solaris requirement of a Stable
	library since they don't allow any functions to be added.
Work Around
N/A
Comments
N/A