diff options
| author | Nikos Mavrogiannopoulos <nmav@gnutls.org> | 2011-08-08 22:58:31 +0200 |
|---|---|---|
| committer | Nikos Mavrogiannopoulos <nmav@gnutls.org> | 2011-08-08 22:58:31 +0200 |
| commit | 7e70042b268ea935d7fd719a3f540222f30edf3c (patch) | |
| tree | 366ab4364d1a4ca639eb78d2102f85686dfbbf46 | |
| parent | 2cfb179d19007a983869314e873ac347de542778 (diff) | |
| download | gnutls-7e70042b268ea935d7fd719a3f540222f30edf3c.tar.gz | |
document new config files of p11-kit.
| -rw-r--r-- | doc/cha-cert-auth.texi | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/cha-cert-auth.texi b/doc/cha-cert-auth.texi index ff50a8ae9b..19f4b9ef2e 100644 --- a/doc/cha-cert-auth.texi +++ b/doc/cha-cert-auth.texi @@ -341,14 +341,13 @@ shared cryptographic keys and certificates in a uniform way, as in the following @image{pkcs11-vision} @subsection Initialization -To allow all the @acronym{GnuTLS} applications to access @acronym{PKCS #11} tokens -it is adviceable to use @code{/etc/gnutls/pkcs11.conf}. This file has the following -format: +To allow all the @acronym{GnuTLS} applications to access @acronym{PKCS} #11 tokens +you can use a configuration per module, such as @code{/etc/pkcs11/modules/mymodule.conf}. +This file has the following format: -@verbatim -load=/usr/lib/opensc-pkcs11.so -load=/usr/lib/gnome-keyring/gnome-keyring-pkcs11.so -@end verbatim +@smallexample +module: /usr/lib/opensc-pkcs11.so +@end smallexample If you use this file, then there is no need for other initialization in @acronym{GnuTLS}, except for the PIN and token functions. Those allow retrieving a PIN |