From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Date: Sat, 19 Jun 2010 14:32:12 +0000 (+0200)
Subject: Added gnutls_sec_param_to_pk_bits() discussion.
X-Git-Tag: gnutls_2_11_3~164
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=72ee34e055b4e998966a115de0c86e39b3831aba;p=thirdparty%2Fgnutls.git

Added gnutls_sec_param_to_pk_bits() discussion.
---

diff --git a/doc/cha-intro-tls.texi b/doc/cha-intro-tls.texi
index 92fb182bda..7b2d06b0b8 100644
--- a/doc/cha-intro-tls.texi
+++ b/doc/cha-intro-tls.texi
@@ -595,6 +595,20 @@ table that extends beyond the key sizes given above.
 
 The recommendations are fairly consistent.
 
+When using @acronym{GnuTLS} and 
+bit sizes are required as input it is recommended to use the following
+functions:
+@itemize
+
+@item @ref{gnutls_pk_bits_to_sec_param}
+
+@item @ref{gnutls_sec_param_to_pk_bits}
+
+@end itemize
+Those functions will convert a human understandable security parameter
+of @code{gnutls_sec_param_t} type, to a number of bits suitable for a public 
+key algorithm.
+
 @node On SSL 2 and older protocols
 @section On SSL 2 and Older Protocols
 @cindex SSL 2