diff options
| author | Attila Molnar <attilamolnar@hush.com> | 2016-02-06 18:01:33 +0100 |
|---|---|---|
| committer | Attila Molnar <attilamolnar@hush.com> | 2016-02-06 18:01:33 +0100 |
| commit | eb84c514e572000c4b909377b4672fb9e1626f8f (patch) | |
| tree | 941eca0de6af2c4229ba05ef49e02aaacd8e2c0a /doc/cha-tokens.texi | |
| parent | 10883e91dfd4a76547f6116f55b577b156d30803 (diff) | |
| download | gnutls-eb84c514e572000c4b909377b4672fb9e1626f8f.tar.gz | |
doc: Fix some typos
Diffstat (limited to 'doc/cha-tokens.texi')
| -rw-r--r-- | doc/cha-tokens.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/cha-tokens.texi b/doc/cha-tokens.texi index 867c8273a6..3310561314 100644 --- a/doc/cha-tokens.texi +++ b/doc/cha-tokens.texi @@ -4,7 +4,7 @@ In several cases storing the long term cryptographic keys in a hard disk or even in memory poses a significant risk. Once the system they are stored is compromised the keys must be replaced as the secrecy of future sessions -is no longer guarranteed. Moreover, past sessions that were not protected by a +is no longer guaranteed. Moreover, past sessions that were not protected by a perfect forward secrecy offering ciphersuite are also to be assumed compromised. If such threats need to be addressed, then it may be wise storing the keys in a security @@ -287,7 +287,7 @@ storage module@footnote{@url{http://p11-glue.freedesktop.org/trust-module.html}} @node PKCS11 Initialization @subsection Initialization -To allow all @acronym{GnuTLS} applications to transparently access smard cards +To allow all @acronym{GnuTLS} applications to transparently access smart cards and tokens, @acronym{PKCS} #11 is automatically initialized during the first call of a @acronym{PKCS} #11 related function. The initialization process, based on p11-kit configuration, loads any appropriate modules. The p11-kit configuration |