summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Release version 0.10Stef Walter2012-01-032-1/+4
|
* Fix build warning on mingw64Stef Walter2012-01-021-1/+1
|
* Compile CuTest.c separately.Andreas Metzler2011-12-237-13/+9
| | | | | Use regular compile and link instead of having #include "CuTest.c" in every test. Works around gcc optimization issue.
* Reorganize tests, work around optimization bugStef Walter2011-12-201-23/+22
| | | | | | | | * Encountered a gcc optimization bug in gcc 4.6.1 which seems to be reordering related function calls eroneously. This bug seems to be fixed in 4.6.2. * Reorganize test code to get around this bug building on mingw, and ubuntu 11.10, both of which use gcc 4.6.1
* Run tests correctly in automakeAndreas Metzler2011-12-091-4/+1
| | | | * This allows failing tests to stop the build
* Build fix for MinGW w64Michael Cronenworth2011-11-251-1/+7
|
* Release version 0.9Stef Walter2011-11-143-3/+9
|
* Reduce autofoo dependenciesStef Walter2011-11-021-2/+2
| | | | | * automake 1.10 (although can benefit from some 1.11 features) * autoconf 2.61
* An intelligent error message when gettextize is not aroundStef Walter2011-11-011-1/+1
|
* p11-kit can't be used as a static libraryStef Walter2011-10-301-0/+4
| | | | | | * It just doesn't make sense. * The initialization refcounting in particular can only work as a shared library.
* Fix problems crashing when freeing TLS on windowsStef Walter2011-10-291-0/+2
|
* Add debug output to windows init and uninit of libraryStef Walter2011-10-291-1/+8
|
* Make build not depend on gtk-doc or pkg-configStef Walter2011-10-291-2/+51
| | | | | | | | * If enabled, gtk-doc can be used, but we no longer expect the gtkdoc autoconf/automake macro files to be installed. * pkg-config is no longer used for checks. * We still do install pkg-config files, and this is the preferred way to build against and link to p11-kit.
* Handle build case when gettextize is not available or not installedStef Walter2011-10-291-1/+7
|
* Fix build with clangStef Walter2011-10-272-15/+0
| | | | * Just removed some unused functions that used GNUC extensions
* Fix broken build on cygwin and mingwDr. Volker Zell2011-10-251-0/+2
| | | | * Add correct linking options for libintl
* Fix broken build on windowsMichael Cronenworth2011-10-251-1/+1
| | | | | * The debug_init() call needed a rename to _p11_debug_init() to match the non-Win32 code.
* Release version 0.8Stef Walter2011-10-243-3/+10
|
* More fixes for non-static function namesStef Walter2011-10-246-56/+53
| | | | | * See previous commit * Initialize library before debug statements
* Rename non-static functions to have a _p11_xxx prefix.Stef Walter2011-10-2422-459/+484
| | | | | | | * Work around issues with brain-dead linkers not respecting the libtool -export-symbol-regex argument https://bugs.freedesktop.org/show_bug.cgi?id=42020
* Initial port to win32Stef Walter2011-10-1723-180/+952
| | | | | | | | * Tests do not all yet pass, at least not on wine * Added abstraction of some non-portable functions in compat.h/c * Build with an argument like this for win32 support: ./autogen.sh --host=i586-mingw32msvc * This win32 port needs more work from interested parties
* Fix up the build options.Stef Walter2011-10-101-57/+66
| | | | | | * --enable-debug turns off optimization * --disable-debug turns off debugging output, debug symbols * --enable-strict turns on -Werror
* Only call C_Initialize and C_Finalize once per moduleStef Walter2011-10-103-58/+168
| | | | | | | | * Do not concurretnly call C_Initialize or C_Finalize in a module * The PKCS#11 spec indicates that mone thread should call those functions. * It's reasonable for a module to expect to only be initialized or finalized in one thread. * In particular NSS does not lock its C_Initialize or C_Finalize.
* Combine initialization testsStef Walter2011-10-103-110/+36
|
* Don't allow recursive calling of C_Initialize on a given module.Stef Walter2011-10-103-3/+114
|