p11-kit.git - Clone of https://github.com/p11-glue/p11-kit

	Commit message (Collapse)	Author	Age	Files	Lines
*	common: New public pkcs11x.h header containing extensions	Stef Walter	2014-09-10	1	-454/+4
\| \| \| \| \| \| \|	Move our internal stuff to pkcs11i.h, and install the pkcs11x.h header containing extensions. https://bugs.freedesktop.org/show_bug.cgi?id=83495
*	common: Change the CKA_X_PUBLIC_KEY_INFO constant to CKA_PUBLIC_KEY_INFO	Stef Walter	2014-09-10	1	-1/+5
\| \| \| \| \| \| \| \| \|	CKA_PUBLIC_KEY_INFO is defined in the PKCS#11 2.40 draft, so use that rather than defining our own. * Fixed up by Nikos Mavrogiannopoulos <nmav@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=83495
*	trust: Port to use CKA_PUBLIC_KEY_INFO and updated trust store spec	Stef Walter	2013-07-04	1	-0/+1
\| \| \| \| \| \| \| \| \| \|	* Use the concepts and PKCS#11 objects described in the recently updated (still work in progress) storing trust spec. * Define our own CKA_X_PUBLIC_KEY_INFO define for now, since the the CKA_PUBLIC_KEY_INFO isn't defined yet. * Most notably, the association between certificates and stapled extensions is by public key. * Rework some of the tests to take into account the above.
*	Add subclassable CK_X_FUNCTION_LIST	Stef Walter	2013-05-15	1	-0/+438
\| \| \| \| \| \| \| \| \| \|	One of the flaws in PKCS#11 for our usage is that each PKCS#11 module is not passed the pointer to the function list, ie: the vtable Here we define a new function list vtable, where each PKCS#11 function takes the vtable itself as the first argument. We use this new list internally to represent subclassable PKCS#11 modules for various features.
*	trust: Use the new NSS PKCS#11 extension codes	Stef Walter	2013-03-08	1	-29/+30
\| \| \| \| \|	NSS had subtly changed the values of the distrust CK_TRUST codes so update them to stay in sync.
*	Move the pkcs11.h header files into common directory	Stef Walter	2013-01-09	1	-0/+155
	* Allows use of them across the whole project * Put a stub file in the p11-kit/ directory, so we can still refer to the headers using that path, which is what it will be at when in the installed includes directory.