summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Move debug and library code into the common/ subdirectoryStef Walter2013-01-0970-1651/+1746
| | | | | | | | | | | Start using p11_ as our internal prefix rather than _p11_. We explicitly export p11_kit_ so this is fine as far as visibility. Move the threading, mutex, and module compat, dict, and array code into the common directory too. Take this opportunity to clean up a bit of internal API as well, since so many lines are being touched internally.
* Fix leak when initializing the proxy modulePankaj Sharma2013-01-091-0/+2
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=58704
* Documentation fixes for PIN functionsStef Walter2013-01-091-6/+6
|
* Fix file descriptor leak in p11_kit_pin_file_callback()Pankaj Sharma2013-01-091-0/+2
| | | | | | * Close the file descriptor used to read the the pin file https://bugs.freedesktop.org/show_bug.cgi?id=58706
* Distribute HACKING in the tarballStef Walter2013-01-081-1/+3
|
* Fix documentation warnings.Stef Walter2013-01-073-5/+9
| | | | | | * P11_KIT_URI_NO_MEMORY is an unexpected state, that will probably never actually be returned. But kept for API compatibility. * make distcheck doc fix
* Guarantee that the key is freed when replacedStef Walter2013-01-073-35/+102
| | | | | | | | | * When setting a key in a map that already exists, then free the old key and replace with the new one. * Fix related bug where key was not properly allocated * Add tests for this https://bugs.freedesktop.org/show_bug.cgi?id=59087
* Don't complain if we cannot access ~/.pkcs11/pkcs11.confStef Walter2012-11-142-9/+34
| | | | | | | * If a process is running under selinux it may not be able to access the home directory of the uid that it is running as. https://bugs.freedesktop.org/show_bug.cgi?id=57115
* Refuse to load the p11-kit-proxy.so as a registered moduleStef Walter2012-09-183-9/+13
| | | | | | | | | | * Since p11-kit-proxy.so is a symlink to the libp11-kit.so library we check that we are not calling into our known CK_FUNCTION_LIST for the proxy code. * Although such a configuration is invalid, detecting this directly prevents strange initialization loop issues that are hard to debug. https://bugs.freedesktop.org/show_bug.cgi?id=55052
* Don't fail initialization if last initialized module failsStef Walter2012-09-181-4/+6
| | | | | | | | | | * We weren't resetting the result code after a failure, so even though failures for critical modules didn't interrupt the initialization loop, the result still leaked to callers. * Also print an error message clearly indicating that a module failed to initialize, regardless of whether critical or not. https://bugs.freedesktop.org/show_bug.cgi?id=55051
* Release version 0.14Stef Walter2012-09-062-1/+9
|
* Change the default of 'user-config' to merge.Stef Walter2012-09-063-5/+5
| | | | | | | * This allows user configured PKCS#11 modules by default. * Admins can change this to 'none' in /etc/pkcs11/pkcs11.conf to go back to the previous behavior. * Posted to the mailing list.
* configure.ac: Fix bogus comma, and fix up spacingAntoine Jacoutot2012-08-231-5/+5
| | | | | | * Fixes a mistake in the previous commit https://bugs.freedesktop.org/show_bug.cgi?id=53706
* Use AC_LANG_PROGRAM to detect program_invocation_short_name functionalityAntoine Jacoutot2012-08-211-2/+7
| | | | | | Were erroneusly detecting program_invocation_short_name on OpenBSD https://bugs.freedesktop.org/show_bug.cgi?id=53706
* Fix build on solarisRob McMahon2012-07-312-1/+7
| | | | | | | * Conditional inclusion of the errno.h header * Link librt when appropriate for nanosleep https://bugs.freedesktop.org/show_bug.cgi?id=52261
* Always encode the "id" attribute in URIsDan Winship2012-07-282-11/+15
| | | | | | Per recommendation of the spec. https://bugs.freedesktop.org/show_bug.cgi?id=52606
* Initialize mutexes correctly in mock moduleStef Walter2012-07-262-1/+6
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Fix warning on windowsStef Walter2012-07-261-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Don't rely on loading order for duplicate modulesStef Walter2012-07-265-6/+15
| | | | | | | | * We had relied on module 'two' loading before 'two-duplicate' in the conf tests. However this isn't always the case, and the name of the module can end up as 'two-duplicate' https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Use Windows thread ids instead of handles for comparisonsStef Walter2012-07-262-6/+11
| | | | | | | | | | * It seems that the HANDLE's returned from GetCurrentThread are often equal for two threads. GetCurrentThreadID doesn't have this problem. * Separate our cross platform thread_t and thread_id_t types even though on unix they're the same thing. https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Use correct shared library extension on windowsStef Walter2012-07-268-1/+37
| | | | | | | | * The windows shared libraries have the .dll extension * This means we also need separate directories for the test module configs on win32 https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Use '.module' extension on module configsStef Walter2012-07-2410-20/+82
| | | | | | | | | | | | | * And want alphanumeric/_.- filenames * Currently this is just a warning, soon it will be enforced * The name of a module does not include the extension Andreas Metzler and Ubuntu both worked on this patch, and I've made some more changes. See https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/911436 https://bugs.freedesktop.org/show_bug.cgi?id=52158
* Fix compiler warning about uninitialized variableStef Walter2012-07-241-1/+1
|
* Don't use strict aliasing during compilationStef Walter2012-07-241-1/+2
| | | | | * Due to the way in which we pass pointers of different types to _p11_hash_iter_next()
* Fix getprogname() running under wineStef Walter2012-07-171-2/+5
| | | | * Wine uses normal slashes instead of backslashes on windows
* Use EFBIG as the error code when pin file is too largeStef Walter2012-07-172-2/+2
| | | | * The previous EOVERFLOW was not supported on mingw
* Don't define duplicate symbolsStef Walter2012-07-171-1/+1
| | | | * clang was giving a build failure here.
* Release version 0.13Stef Walter2012-07-162-1/+15
|
* Don't allow reading of pin files larger than 4096 bytesStef Walter2012-06-293-7/+91
| | | | * p11_kit_pin_file_callback() only returns pins up to 4096 bytes now
* Win32 build fixesStef Walter2012-06-294-30/+10
| | | | | | * Remove unused functions * Use getprogname() instead of calc_progname() which no longer exists * Fix up exporting of functions in the mock module
* tools: Don't barf when p11-kit -hStef Walter2012-06-271-1/+1
|
* If a module is not marked 'critical' then ignore failureStef Walter2012-06-271-3/+11
| | | | | * Ignore failure when initializing registered modules when 'critical' is not set on a module.
* Fix the flags in pin.hStef Walter2012-06-081-6/+6
| | | | | | | | | * Due to a brain fart the P11_KIT_PIN_* flags were not bit flags but decimal numbers. * This necessarily breaks API/ABI for users of the P11_KIT_PIN_FLAGS_RETRY, P11_KIT_PIN_FLAGS_MANY_TRIES and P11_KIT_PIN_FLAGS_FINAL_TRY flags. But those wouldn't have worked anyway.
* Preconditions to check for input probs and out of memoryStef Walter2012-05-1314-264/+352
| | | | | | * We don't try to guarantee completely robust and problem free behavior in cases where the caller or process isn't behaving. We consider these to be outside of our control.
* Use gcc extensions to check varargs during compileStef Walter2012-05-136-13/+38
| | | | | * Add macros GNUC_PRINTF and GNUC_NULL_TERMINATED to check correct printf and NULL terminated style varargs
* Fix test modules linking errorsStef Walter2012-05-012-0/+3
| | | | * And display warning messages in the debug output
* Provide compat getprogname() implementations on other OS'sStef Walter2012-05-016-64/+81
| | | | * And use them in our replacement err() and p11_kit_set_progname()
* Move the compat.[ch] headers into common directory/Stef Walter2012-04-3014-273/+186
| | | | | * And the compat stuff in the p11-kit directory merged into util.c and util.h
* Doc tweaks for PIN functionalityStef Walter2012-04-161-19/+28
|
* Add tests for enable-in and disable-inStef Walter2012-04-028-28/+171
|
* Build some test modules for testing main p11-kit functionalityStef Walter2012-04-029-22/+225
| | | | * And put together a test for duplicate modules
* Add more p11-kit cleanup to fix valgrind leak reportsStef Walter2012-04-021-0/+11
| | | | | * per-thread memory isn't actually a real memory leak, but was still reachable after exit, so clean this up.
* Fix crasher when a duplicate module is presentStef Walter2012-04-011-6/+7
|
* Add enable-in and disable-in options to module configStef Walter2012-04-0110-4/+346
| | | | | | | | * These can be used to load certain modules in certain programs, or prevent loading in others. * Useful for a key manager like seahorse, so we can load extra modules (think NSS) that other modules shouldn't load.
* Fix broken hashmap behaviorStef Walter2012-03-272-9/+5
| | | | | | | * We were relying on undefined gcc behavior related to the & operator. * This would show up as a test failure when running with -O2 on certain GCC versions, as well as failure on clang 3.1
* Remove p11-kit.pot file from gitStef Walter2012-03-192-343/+1
| | | | * Generated automatically
* Release version 0.12Stef Walter2012-03-092-1/+4
|
* Fix build problem due to pthread extensions usageSimon Josefsson2012-03-081-0/+1
| | | | See: http://ipozgaj.blogspot.com/2006/08/posix-threads-and-manual-pages-rant.htm
* Release 0.11Stef Walter2012-02-073-3/+6
|
* Remove automatic reinitialization of PKCS#11 after forkStef Walter2012-01-231-9/+2
| | | | | | | | | | | | | | * First of all one should only call async-signal-safe functions from the callbacks of pthread_atfork(), and so we cannot reinitialize directly. * Some modules use pthread_atfork() to detect forking and setup their internal state. If we call into them in our pthread_atfork() callback then this is inherently racy. * There was danger of endless loops and deadlocks which are caused by handlers which fork in their C_Initialize * Many processes do fork/exec, reinitializing PKCS#11 for these forks is quite resourc intensive when the child process won't use PKCS#11 at all.