Hi Dave, > This can be worked by checking libraryDescription and libraryVersion in > addition to cryptokiVersion, but that'll be incorrect in the future if > support for these attributes is added to the 2.4 branch between now and > its final release. > > Are there plans to support the full v2.20 spec? Does it make sense to > permit the attributes introduced in v2.20 even if they don't actually do > anything, or will that have unintended consequences? Or should the > library revert to reporting cryptokiVersion == 2.12 until full support > for 2.20 is added?
We don't have pans to support the full 2.20 spec -- our policy has been to bump the cryptokiVersion when we support any part of a new spec though... Kent > If either of the latter two options is preferable, I'd be happy to > submit a patch. > > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
