From ce29564aadc83f3fb72751ca7fd06a1a69de33b6 Mon Sep 17 00:00:00 2001 From: Tim Landscheidt Date: Dec 09 2018 19:48:50 +0000 Subject: Fix asciidoctor warnings --- diff --git a/guidelines/modules/ROOT/pages/Pkcs11Support.adoc b/guidelines/modules/ROOT/pages/Pkcs11Support.adoc index 0ed32d3..0a3f3c2 100644 --- a/guidelines/modules/ROOT/pages/Pkcs11Support.adoc +++ b/guidelines/modules/ROOT/pages/Pkcs11Support.adoc @@ -5,7 +5,7 @@ These guidelines are relevant to maintainers of packages with smart cards driver == Registering the modules system-wide -Any package in Fedora containing a PKCS#11 provider module, intended to be used outside this package, MUST be registered with link:http://p11-glue.freedesktop.org/[p11-kit]. For example, the link:https://github.com/OpenSC/OpenSC/wiki[OpenSC] module which supports most major hardware smart cards, will automatically drop a config file into the appropriate place and then its module will automatically appear in well-behaved software which is integrated with the platform and uses p11-kit properly. The appropriate place in Fedora can be obtained with `pkg-config p11-kit-1 --variable p11_module_configs` or `%{_datadir}/p11-kit/modules/`. The dropped file should have the `.module` suffix and should contain something similar to the contents below (which is the opensc example). +Any package in Fedora containing a PKCS#11 provider module, intended to be used outside this package, MUST be registered with link:http://p11-glue.freedesktop.org/[p11-kit]. For example, the link:https://github.com/OpenSC/OpenSC/wiki[OpenSC] module which supports most major hardware smart cards, will automatically drop a config file into the appropriate place and then its module will automatically appear in well-behaved software which is integrated with the platform and uses p11-kit properly. The appropriate place in Fedora can be obtained with `pkg-config p11-kit-1 --variable p11_module_configs` or `+%{_datadir}/p11-kit/modules/+`. The dropped file should have the `.module` suffix and should contain something similar to the contents below (which is the opensc example). # This file describes how to load the opensc module # See: http://p11-glue.freedesktop.org/doc/p11-kit/config.html @@ -16,7 +16,7 @@ Any package in Fedora containing a PKCS#11 provider module, intended to be used # 32-bit and 64-bit and make them parallel installable module: opensc-pkcs11.so -The provider module, as mentioned in the example below should be installed at `%{_libdir}/pkcs11/`. +The provider module, as mentioned in the example below should be installed at `+%{_libdir}/pkcs11/+`. Once a module is registered the tokens/HSMs provided by it should be listed in the `p11tool` output using the following command: @@ -27,7 +27,7 @@ Once a module is registered the tokens/HSMs provided by it should be listed in t [#registered] == How applications take advantage of registered provider modules -Packages which can potentially use PKCS#11 tokens SHOULD automatically use the tokens which are present in the system's p11-kit configuration, rather than needing to have a PKCS#11 provider explicitly specified. That can be done by applications using the p11-kit library to get the list of modules, or by applications defaulting to the p11-kit proxy module (`%{_libdir}/p11-kit-proxy.so`), if no PKCS#11 provider module was specified by the user. The proxy module, is a single module wrapping all available registered modules. +Packages which can potentially use PKCS#11 tokens SHOULD automatically use the tokens which are present in the system's p11-kit configuration, rather than needing to have a PKCS#11 provider explicitly specified. That can be done by applications using the p11-kit library to get the list of modules, or by applications defaulting to the p11-kit proxy module (`+%{_libdir}/p11-kit-proxy.so+`), if no PKCS#11 provider module was specified by the user. The proxy module, is a single module wrapping all available registered modules. [#specify-card] == How to specify a specific smart card/HSM