/usr/share/doc/p11-kit
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
# p11-kit [](https://github.com/p11-glue/p11-kit/actions?query=workflow%3Atest) [](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, byproviding a way to load and enumerate PKCS #11 modules, as well as astandard configuration setup for installing PKCS #11 modules in such away 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$ meson compile -C _build$ meson test -C _build# meson install -C _build``` If you install it locally for testing purposes, you may want tospecify `-Dsystemd=disabled -Dbash_completion=disabled` at theinvocation of `meson _build`, to avoid installing files to thesystem locations. # 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