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

	Commit message (Collapse)	Author	Age	Files	Lines
*	More compatible path munging and handling code	Stef Walter	2013-04-03	1	-1/+2
\| \| \| \| \| \| \| \| \| \|	Centralize the path handling code, so we can remove unixy assumptions and have a chance of running on Windows. The current goal is to run all the tests on Windows. Includes some code from LRN <lrn1986@gmail.com> https://bugs.freedesktop.org/show_bug.cgi?id=63062
*	Separate library init from message code	Stef Walter	2013-04-03	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	Put library init/uninit code its into their own statically linked library so that they don't get linked into the p11-kit executable. Refactor the message code so that the library initialization can plug in its per thread message buffer. https://bugs.freedesktop.org/show_bug.cgi?id=63046
*	trust: Predictable behavior with duplicate certificates in token	Stef Walter	2013-03-20	1	-15/+4
\| \| \| \| \| \| \| \|	If duplicate certificates are present in a token, we warn about this, and don't really recommend it. However we have predictable behavior where blacklist is prefered to anchor is preferred to unknown trust. https://bugs.freedesktop.org/show_bug.cgi?id=62548
*	trust: Use descriptive labels for tokens	Stef Walter	2013-03-19	1	-2/+20
\| \| \| \| \| \| \| \|	Try to determine which one is the system trust input token, and which one is the default token by using datadir and sysconfdir respectively. https://bugs.freedesktop.org/show_bug.cgi?id=62534
*	trust: Remove the temporary built in distrust objects	Stef Walter	2013-03-19	1	-148/+0
\| \| \| \|	These should now be loaded from the .p11-kit persist format.
*	trust: Add a builder which builds objects out of parsed data	Stef Walter	2013-03-15	1	-5/+16
\| \| \| \| \| \| \| \| \| \| \|	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
*	trust: Refactor to include concept of the index	Stef Walter	2013-03-15	1	-20/+12
\| \| \| \| \| \| \| \| \| \|	* The index holds PKCS#11 objects whether for the token or for the session. * The index provides hook for a builder to expand or validate objects being added to the index. * In addition theres a change hook so that a builder can maintain state between objects, such as the compat NSS trust objects. https://bugs.freedesktop.org/show_bug.cgi?id=62329
*	trust: Make each configured path its own token	Stef Walter	2013-03-15	1	-41/+23
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Each source directory or file configured into the module or passed in as an initialization argument becomes its own token. Previously there was one token that contained certificates from all the configured paths. * These tokens are clearly labeled in the token info as to the directory or file that they represent. * Update PKCS#11 module logic to deal with multiple tokens, validate the slot ids and so on. * The order in which the paths are configured will become the order of trust priority. This is the same order in which they are listed through 'p11-kit list-modules' and C_GetSlotList. * Update the frob-token internal tool to only play with one path * Adjust tests where necessary to reflect the new state of things and add tests for modified trust module code https://bugs.freedesktop.org/show_bug.cgi?id=61499
*	trust: Rework input path treatment	Stef Walter	2013-03-15	1	-26/+52
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Accept a single --with-trust-paths argument to ./configure which cotnains all the input paths. * The --with-system-anchors and --with-system-certificates ./configure arguments are no longer supported. Since they were only present briefly, no provision is made for backwards compatibility. * Each input file is treated as containing anchors by default unless an input certificate contains detailed trust information. * The files in each input directory are not automatically treated as anchors unless a certificate contains detailed trust information. * The files in anchors/ subdirectory of each input directory are automatically marked as anchors. * The files in the blacklist/ subdirectory of each input directory are automatically marked as blacklisted. * Update tests and move around test certificates so we can test these changes. https://bugs.freedesktop.org/show_bug.cgi?id=62327
*	trust: Use the new NSS PKCS#11 extension codes	Stef Walter	2013-03-08	1	-3/+3
\| \| \| \| \|	NSS had subtly changed the values of the distrust CK_TRUST codes so update them to stay in sync.
*	Hard code distrust temporarily.	Stef Walter	2013-03-08	1	-1/+149
\| \| \| \| \|	This is because we have no way to load this data into the trust module. Working on a real solution.
*	trust: Refactor how we load builtin objects	Stef Walter	2013-03-08	1	-11/+13
\|
*	Some debug info about which files are being loaded	Stef Walter	2013-02-05	1	-2/+15
\|
*	Add the builtin roots NSS specific object	Stef Walter	2013-02-05	1	-1/+27
\| \| \| \|	This tells NSS that this is a source of anchors.
*	Add basic trust module	Stef Walter	2013-02-05	1	-0/+256
	This is based off the roots-store from gnome-keyring and loads certificates from a root directory and exposes them as PKCS#11 objects.