summaryrefslogtreecommitdiff
path: root/common/Makefile.am
Commit message (Collapse)AuthorAgeFilesLines
* MOVED TO: https://github.com/p11-glue/p11-kitHEADmasterStef Walter2016-11-291-111/+0
| | | | | | | | | This repository has moved to GitHub to allow further contributions and more flexibility who can merge changes. More details here: https://lists.freedesktop.org/archives/p11-glue/2016-November/000626.html
* common: Use secure_getenv() implementation when setuidStef Walter2014-10-021-1/+7
| | | | | In anything security sensitive, use secure_getenv() implementation for retrieving environment variables.
* common: New public pkcs11x.h header containing extensionsStef Walter2014-09-101-1/+2
| | | | | | | Move our internal stuff to pkcs11i.h, and install the pkcs11x.h header containing extensions. https://bugs.freedesktop.org/show_bug.cgi?id=83495
* Move to non-recursive Makefile for building bins and libsStef Walter2014-08-151-28/+85
| | | | Still use recursive for documentation and translation.
* Reorganize various componentsStef Walter2013-06-251-27/+4
| | | | | | | * p11-kit library and tool in the p11-kit/ subdirectory * trust module and new trust tool in trust/ subdirectory * No more tools/ subdirectory * Lots less in the common/ subdirectory
* Our own unit testing frameworkStef Walter2013-05-211-2/+3
| | | | | | | | * Support the TAP protocol * Much cleaner without having to carry around state * First class support for setup/teardown * Port the common tests * Wait on porting other tests until we've merged outstanding code
* Pull the argv parsing code into its own fileStef Walter2013-05-211-0/+1
| | | | So it can be used from multiple code paths
* More compatible path munging and handling codeStef Walter2013-04-031-0/+1
| | | | | | | | | | Centralize the path handling code, so we can remove unixy assumptions and have a chance of running on Windows. The current goal is to run all the tests on Windows. Includes some code from LRN <lrn1986@gmail.com> https://bugs.freedesktop.org/show_bug.cgi?id=63062
* Separate library init from message codeStef Walter2013-04-031-7/+8
| | | | | | | | | | | 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
* Add a bit of infrastructure for running valgrindStef Walter2013-03-201-1/+2
| | | | | * make memcheck: Runs basic memory checking * make leakcheck: Also runs leak checking
* hash: Rename file and functions for hashesStef Walter2013-03-201-1/+1
| | | | | We're going to be adding other hashes. Also build as part of a different common library.
* trust: Support a p11-kit specific serialization formatStef Walter2013-03-151-0/+2
| | | | | | | This is documented in doc/internals/ subdirectory Add tests for the format as well. https://bugs.freedesktop.org/show_bug.cgi?id=62156
* url: Split out the URL encoding and decoding functionsStef Walter2013-03-151-0/+1
| | | | | | | We want to use these as the format for encoding binary data in our PKCS#11 attribute persistence https://bugs.freedesktop.org/show_bug.cgi?id=62156
* lexer: Make a lexer for our config file formatStef Walter2013-03-151-0/+1
| | | | | | This lexer will be used in our PKCS#11 persistence format as well. https://bugs.freedesktop.org/show_bug.cgi?id=62156
* attrs: Add info functions for constant names and valuesStef Walter2013-03-151-0/+1
| | | | | | | * For retrieving the name and/or nick of constants * The nick is what we'll use in the file format https://bugs.freedesktop.org/show_bug.cgi?id=62329
* Build with the libtasn1 CFLAGS properlyStef Walter2013-03-041-0/+3
| | | | | | Tweaks by: Roman Bogorodskiy <bogorodskiy@gmail.com> https://bugs.freedesktop.org/show_bug.cgi?id=61739
* Use the CN, OU or O of certificates to generate a labelStef Walter2013-02-051-0/+1
| | | | | * This is in cases where the certificate information does not already have a friendly name or alias.
* Refactor how parsing of ASN.1 data and certificate extensions workStef Walter2013-02-051-0/+2
|
* Implement stapled certificate extensions internallyStef Walter2013-02-051-0/+1
| | | | | | | | | | | | * Use stapled certificate extensions to represent loaded trust policy * Build NSS trust objects from stapled certificate extensions * Add further attribute debugging for NSS trust objects * Use a custom certificate extension for the OpenSSL reject purpose data * Use SubjectKeyIdentifier for OpenSSL keyid data * Use ExtendedKeyUsage for OpenSSL trust purpose data * Implement simple way to handle binary DER OIDs, using the DER TLV length. DER OIDs are used in the CKA_OBJECT_ID value, and elsewhere. * Split out the building of NSS trust objects from the main parser
* Add support for openssl TRUSTED CERTIFICATE PEM filesStef Walter2013-02-051-0/+2
|
* Add support for parsing PEM filesStef Walter2013-02-051-0/+2
|
* Add basic trust moduleStef Walter2013-02-051-4/+11
| | | | | | 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 basic checksum algorithmsStef Walter2013-02-051-0/+9
| | | | | | The SHA-1 and MD5 digests here are used for checksums in legacy protocols. We don't use them in cryptographic contexts at all. These particular algorithms would be poor choices for that.
* Add more mock-module implementationStef Walter2013-02-041-0/+5
| | | | | * Move mock code into the common/ directory to be used by multiple components of p11-kit
* Add generic buffer codeStef Walter2013-02-041-0/+1
| | | | Represents a block of memory that can be added to, parsed and so on
* Add common functions for manipulating CK_ATTRIBUTE arraysStef Walter2013-01-091-0/+1
|
* Move the pkcs11.h header files into common directoryStef Walter2013-01-091-0/+7
| | | | | | | * Allows use of them across the whole project * Put a stub file in the p11-kit/ directory, so we can still refer to the headers using that path, which is what it will be at when in the installed includes directory.
* Build common code into noinst librariesStef Walter2013-01-091-2/+10
| | | | | | * This is cleaner than building the same source files all over the place over and over. * Works better with code coverage.
* Move debug and library code into the common/ subdirectoryStef Walter2013-01-091-0/+11
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.