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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Avoid multiple stat() calls for same file	Stef Walter	2013-08-28	1	-0/+1
\| \| \| \| \| \|	As a side effect we can also not use the dirent.d_type field https://bugs.freedesktop.org/show_bug.cgi?id=68525
*	trust: Explicitly specify which formats parser should parse	Stef Walter	2013-07-08	1	-2/+16
\|
*	trust: Implement reloading of token data	Stef Walter	2013-07-03	1	-3/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Reload token data whenever a new session is opened. * Only reload files/directories that have changed. * Move duplicate anchor/blacklist detection logic into the extract code. This is in line with the approach being discussed on the mailing lists and spec document. * New internal attribute CKA_X_ORIGIN set on all objects so we can track where an object came from, and replace it when reloaded. In general this is a prerequisite for modification of objects reload before modify is necessary to prevent multiple callers clobbering each other's changes.
*	trust: Add a builder which builds objects out of parsed data	Stef Walter	2013-03-15	1	-33/+12
\| \| \| \| \| \| \| \| \| \| \|	The builder completes the objects from the parsed data and takes over the responsibilities that the parser and adapter previously shared. This is necessary to prepare for arbitrary data coming from the p11-kit specific input files. https://bugs.freedesktop.org/show_bug.cgi?id=62329
*	Refactor how parsing of ASN.1 data and certificate extensions work	Stef Walter	2013-02-05	1	-13/+1
\|
*	Fill in certificate authority and trust data correctly	Stef Walter	2013-02-05	1	-2/+9
\| \| \| \| \| \| \| \| \| \| \| \|	* Fill in CKA_CERTIFICATE_CATEGORY properly for authorities based on the presence of BasicConstraints and/or v1 certificates * Fill in CKA_TRUSTED and CKA_X_DISTRUSTED based on whether the parser is running for anchors or blacklist * In addition support the concept of blacklisted certificates mixed in with the anchors (without any purposes) since that's what exists in the real world. * We do this after the various hooks have had a chance to mess with the certificate extensions and such.
*	Implement stapled certificate extensions internally	Stef Walter	2013-02-05	1	-24/+15
\| \| \| \| \| \| \| \| \| \| \| \|	* Use stapled certificate extensions to represent loaded trust policy * Build NSS trust objects from stapled certificate extensions * Add further attribute debugging for NSS trust objects * Use a custom certificate extension for the OpenSSL reject purpose data * Use SubjectKeyIdentifier for OpenSSL keyid data * Use ExtendedKeyUsage for OpenSSL trust purpose data * Implement simple way to handle binary DER OIDs, using the DER TLV length. DER OIDs are used in the CKA_OBJECT_ID value, and elsewhere. * Split out the building of NSS trust objects from the main parser
*	Add basic trust module	Stef Walter	2013-02-05	1	-0/+108
	This is based off the roots-store from gnome-keyring and loads certificates from a root directory and exposes them as PKCS#11 objects.