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

	Commit message (Collapse)	Author	Age	Files	Lines
*	pkg-config: Expose p11_trust_paths variable	Daiki Ueno	2016-11-15	1	-0/+1
\| \| \| \| \|	The variable is mentioned in the manual but wasn't exposed from the pkg-config.
*	trust: Rework input path treatment	Stef Walter	2013-03-15	1	-3/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* 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
*	Add basic trust module	Stef Walter	2013-02-05	1	-0/+3
\| \| \| \| \| \|	This is based off the roots-store from gnome-keyring and loads certificates from a root directory and exposes them as PKCS#11 objects.
*	Add a /usr/share/p11-kit/modules directory for package module configs	Stef Walter	2013-02-05	1	-6/+7
\| \| \| \| \| \|	* Try to make /etc/pkcs11/modules for administrator use * Override the old pkg-config variables to help packages start using the new location
*	When a module has a relative path, load it from $libdir/pkcs11	Kalev Lember	2011-09-14	1	-0/+1
\| \| \| \| \| \| \|	So far we have only supported full paths to the pkcs11 modules in config files. This change adds relative path support, so that for modules installed under the standard $libdir/pkcs11, the config file won't have to spell out the full path.
*	Rename pkgconfig configuration directory variables	Kalev Lember	2011-09-14	1	-4/+6
\| \| \| \| \| \| \| \| \| \| \| \|	Renamed them to reduce ambiguity and to pave the way for exposing some additional parameters. p11_system_modules -> p11_system_config_modules p11_user_modules -> p11_user_config_modules configure --with-pkcs11-dir => configure --with-system-config
*	Create a link for the proxy module.	Stef Walter	2011-07-27	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \|	* Install proxy module at its own path which is not prefixed by 'lib' * Since the proxy module is the same as the library, and actually needs to be loaded as the same library in memory (due to resource tracking per process), use a symlink for proxy. * Add a variable to the pkg-config file which shows the path to the proxy module. ie: $ pkg-config --variable=proxy_module p11-kit-1 https://bugzilla.redhat.com/show_bug.cgi?id=725905
*	Change around installation of headers, pkg-config, and file names	Stef Walter	2011-05-27	1	-0/+17
	* Install headers to ${prefix}/include/p11-kit-1/p11-kit/ * This solves problems with other projects that have their own pkcs11.h files. * Change the pkg-config file name to p11-kit-1.pc * Change the source file names.