diff options
| author | Nikos Mavrogiannopoulos <nmav@gnutls.org> | 2011-07-31 13:03:58 +0200 |
|---|---|---|
| committer | Nikos Mavrogiannopoulos <nmav@gnutls.org> | 2011-07-31 13:03:58 +0200 |
| commit | 199ef70e8d1fb87f3547f2cdb0edd20f68d4febd (patch) | |
| tree | 7e549c6edf2807e6e9524e495b9f6a2dfa58bd95 /doc/cha-cert-auth.texi | |
| parent | 3b0b75ab6d15cba8758248f451be0c86c28a3e22 (diff) | |
| download | gnutls-199ef70e8d1fb87f3547f2cdb0edd20f68d4febd.tar.gz | |
documentation updates.
Diffstat (limited to 'doc/cha-cert-auth.texi')
| -rw-r--r-- | doc/cha-cert-auth.texi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/cha-cert-auth.texi b/doc/cha-cert-auth.texi index ae2df5dbdf..437c68d034 100644 --- a/doc/cha-cert-auth.texi +++ b/doc/cha-cert-auth.texi @@ -392,7 +392,7 @@ such as @acronym{Gnome Keyring}. The objects residing on such token can be certificates, public keys, private keys or even plain data or secret keys. Of those certificates and public/private key pairs can be used with @acronym{GnuTLS}. Its main advantage is that it allows operations on private key objects such as decryption -and signing without accessing the key itself. +and signing without exposing the key. Moreover it can be used to allow all applications in the same operating system to access shared cryptographic keys and certificates in a uniform way, as in @ref{fig:pkcs11-vision}. @@ -404,8 +404,8 @@ shared cryptographic keys and certificates in a uniform way, as in @ref{fig:pkcs @subsection Initialization To allow all the @acronym{GnuTLS} applications to access @acronym{PKCS} #11 tokens -it is advisable to use @code{/etc/pkcs11/modules/mymodule.conf}. This file has the following -format: +you can use a configuration per module, such as @code{/etc/pkcs11/modules/mymodule.conf}. +This file has the following format: @smallexample module: /usr/lib/opensc-pkcs11.so |