From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Date: Wed, 18 Jul 2012 18:56:49 +0000 (+0200)
Subject: mention the context specific PIN functions.
X-Git-Tag: gnutls_3_1_0pre0~41
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8b80cadefce7584097812dd6e9cce683e463bbcc;p=thirdparty%2Fgnutls.git

mention the context specific PIN functions.
---

diff --git a/doc/cha-tokens.texi b/doc/cha-tokens.texi
index b9c25dbf44..9ec516460e 100644
--- a/doc/cha-tokens.texi
+++ b/doc/cha-tokens.texi
@@ -208,7 +208,10 @@ multiple users.
 
 To avoid conflicts with multiple registered callbacks for PIN functions,
 @funcref{gnutls_pkcs11_get_pin_function} may be used to check for any previously
-set functions.
+set functions. In addition context specific PIN functions are allowed, e.g., by
+using functions below.
+
+@showfuncC{gnutls_certificate_set_pin_function,gnutls_pubkey_set_pin_function,gnutls_privkey_set_pin_function}
 
 Moreover PKCS #11 modules must be reinitialized on the child processes
 after a @funcintref{fork}. @acronym{GnuTLS} provides @funcref{gnutls_pkcs11_reinit}