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

	Commit message (Collapse)	Author	Age	Files	Lines
*	uri: Make scheme comparison case-insensitive	Daiki Ueno	2018-05-25	1	-0/+21
\| \| \| \| \|	RFC 3986 suggests that implementations should accept uppercase letters as equivalent to lowercase in scheme names.
*	test: Add checks for duplicate vendor attributes	Daiki Ueno	2017-08-08	1	-0/+10
\|
*	uri: Support vendor query attributes	Daiki Ueno	2017-02-21	1	-0/+40
\| \| \| \| \| \| \| \|	If an unknown attribute is present in the query part of the PKCS#11 URI, the parser treated it as unrecognized and subsequent matches failed. Instead, keep track of such attributes and provide a set of API to deal with them.
*	uri: Support query attributes to specify module	Daiki Ueno	2017-01-19	1	-0/+115
\| \| \| \| \|	Accept and produce 'module-name' and 'module-path' query attributes defined in RFC 7512.
*	uri: fix producing the query attributes	Lubomir Rintel	2017-01-12	1	-1/+1
\| \| \| \|	Put the pin-* attributes where they belong: to the query part.
*	uri: fix the query attribute parsing	Lubomir Rintel	2017-01-12	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \|	The pin-* attributes belong to the query part. We should not parse them until we see a '?' and they're separated with a '&'. This might be an important thing -- some of the query attributes may have security implications reaching outside scope of the token itself, to the host system itself. E.g. a pin-source may cause the consumer to access a file or module-path (unimplemented) execute code. The user may want to just chop the attribute part off if they want the consumer access the token and not take the security considerations into account.
*	uri: Support 'slot-id' path attribute	Daiki Ueno	2016-09-02	1	-0/+47
\| \| \| \| \| \|	Accept 'slot-id' path attribute defined in RFC 7512. https://bugs.freedesktop.org/show_bug.cgi?id=97245
*	uri: Support slot info path attributes	Daiki Ueno	2016-09-02	1	-0/+70
\| \| \| \| \| \| \|	Accept 'slot-description' and 'slot-manifacturer' path attributes defined in RFC 7512. https://bugs.freedesktop.org/show_bug.cgi?id=97245
*	Generate URIs compliant to the PKCS#11 URI draft in LC	Nikos Mavrogiannopoulos	2015-02-20	1	-13/+13
\| \| \| \| \| \| \| \| \| \| \| \|	We continue to accept both the older style 'object-type' field in addition to the new 'type' field. However we start generating URIs in the new form. In other words we have backwards compatibility, but not forwards compatibility. Given the fact that PKCS#11 URIs are now standardizing this is an acceptable compromise. https://bugs.freedesktop.org/show_bug.cgi?id=86474
*	Added test for pin-value	Nikos Mavrogiannopoulos	2015-02-20	1	-0/+54
\| \| \| \| \| \| \|	https://bugs.freedesktop.org/show_bug.cgi?id=87582 Signed-off-by: Stef Walter <stefw@redhat.com> * Added test for bad encoded pin-value in uri
*	uri: Accept 'type' in additon to 'object-type' in PKCS#11 URIs	Stef Walter	2014-11-14	1	-0/+27
\| \| \| \|	This was a later change to the PKCS#11 specification drafts
*	Move to non-recursive Makefile for building bins and libs	Stef Walter	2014-08-15	1	-0/+1314
	Still use recursive for documentation and translation.