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

	Commit message (Collapse)	Author	Age	Files	Lines
*	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
*	extract: Make extracted output directories read-only	Stef Walter	2013-03-19	1	-16/+44
\| \| \| \| \| \|	This is not a security feature or anything like that, but a hint that the files are managed by the extract tool and should not be modified manually.
*	extract: Allow p11_save_write() to automatically calculate length	Stef Walter	2013-03-15	1	-2/+9
\| \| \| \| \| \| \| \| \|	Also if automatically calculating length, then ignore input that is NULL, as something that shouldn't be written out. This allows easier chaining of optional output, such as comments. https://bugs.freedesktop.org/show_bug.cgi?id=62029
*	Windows doesn't support symlinks, chmod, or atomic renames	Stef Walter	2013-03-03	1	-2/+42
\| \| \| \| \| \| \|	* Don't create symlinks on windows * No atomic renames, so delete and then rename * Make sure to close files before unlinking on windows * No chmod permissions on windows
*	Support for sane writing to files extracted	Stef Walter	2013-02-05	1	-0/+462
	* Implement atomic writes of files * Writing with checks that not overwriting anything unless desired * Writing and overwriting of directory contents in a robust way