summaryrefslogtreecommitdiff
path: root/doc/cha-tokens.texi
diff options
context:
space:
mode:
authorNikos Mavrogiannopoulos <nmav@redhat.com>2016-04-22 09:26:55 +0200
committerNikos Mavrogiannopoulos <nmav@redhat.com>2016-04-22 09:26:55 +0200
commit6d64e7bed34cad78a6645b1527d361ac9dc82e06 (patch)
tree08ce80f0e5e4b41a0cc2f23b0d6ed001cf43c351 /doc/cha-tokens.texi
parent0b2ad185b65e41771cf2b3fb71a43e86d727a444 (diff)
downloadgnutls-6d64e7bed34cad78a6645b1527d361ac9dc82e06.tar.gz
doc: document the TPM 1.2 limitation
Diffstat (limited to 'doc/cha-tokens.texi')
-rw-r--r--doc/cha-tokens.texi1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/cha-tokens.texi b/doc/cha-tokens.texi
index a956771f40..754592269b 100644
--- a/doc/cha-tokens.texi
+++ b/doc/cha-tokens.texi
@@ -476,6 +476,7 @@ accessing them. That is very similar to the operation of a @acronym{PKCS} #11 sm
The chip allows for storage and usage of RSA keys, but has quite some
operational differences from @acronym{PKCS} #11 module, and thus require different handling.
The basic TPM operations supported and used by GnuTLS, are key generation and signing.
+That support is currently limited to TPM 1.2.
The next sections assume that the TPM chip in the system is already initialized and
in a operational state. If not, ensure that the TPM chip is enabled by your BIOS,