/
usr
/
share
/
doc
/
p11-kit
/
/usr/share/doc/p11-kit
mkdir
upload
Name
Size
Mode
Actions
AUTHORS
36
0644
edit
dl
rm
NEWS
17277
0644
edit
dl
rm
pkcs11.conf.example
390
0644
edit
dl
rm
README
1785
0644
edit
dl
rm
Edit:
/usr/share/doc/p11-kit/README
(1785B)
# p11-kit [](https://travis-ci.org/p11-glue/p11-kit) [](https://coveralls.io/r/p11-glue/p11-kit) [](https://bestpractices.coreinfrastructure.org/en/projects/1627) [](https://lgtm.com/projects/g/p11-glue/p11-kit/alerts/) [](https://lgtm.com/projects/g/p11-glue/p11-kit/context:cpp) p11-kit aims to solve problems with coordinating the use of [PKCS #11] by different components or libraries living in the same process, by providing a way to load and enumerate PKCS #11 modules, as well as a standard configuration setup for installing PKCS #11 modules in such a way that they're discoverable. # Documentation * [Main site](https://p11-glue.github.io/p11-glue/p11-kit.html) * [Manual](https://p11-glue.github.io/p11-glue/p11-kit/manual/) # Building To build and install p11-kit, you can use the following commands: ```console $ meson _build $ ninja -C _build $ ninja -C _build test # ninja -C _build install ``` If you install it locally for testing purposes, you may want to specify `-Dsystemd=disabled -Dbash_completion=disabled`. # Releases Releases are made available via the [primary github site](https://github.com/p11-glue/p11-kit/releases). They are signed with the current maintainer's [OpenPGP key](https://keys.openpgp.org/search?q=462225C3B46F34879FC8496CD605848ED7E69871). [PKCS #11]: https://en.wikipedia.org/wiki/PKCS_11
Save
cmd:
run