summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2011-06-13 17:15:38 (GMT)
committerWerner Koch <wk@gnupg.org>2011-06-13 17:15:38 (GMT)
commitb90be2836e1806f2441c97f70952ca042a67f520 (patch)
treec1326093798b5839fa556fca2b727f590c6a22b2
parentc4bce4aa60e62b55e2f7781a2aa55c2e30db2112 (diff)
downloadlibgcrypt-b90be2836e1806f2441c97f70952ca042a67f520.tar.gz
libgcrypt-b90be2836e1806f2441c97f70952ca042a67f520.tar.xz
Suggest to use GCRYMPI_FMT_USG with gcry_sexp_nth_mpi.
-rw-r--r--doc/gcrypt.texi12
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/gcrypt.texi b/doc/gcrypt.texi
index bdfe955..419dc68 100644
--- a/doc/gcrypt.texi
+++ b/doc/gcrypt.texi
@@ -2366,10 +2366,10 @@ appropriate MPI using this expression for @var{data}:
@end example
@noindent
-This has the same semantics as the old style MPI only way. @var{MPI} is
-the actual data, already padded appropriate for your protocol. Most
-systems however use PKCS#1 padding and so you can use this S-expression
-for @var{data}:
+This has the same semantics as the old style MPI only way. @var{MPI}
+is the actual data, already padded appropriate for your protocol.
+Most RSA based systems however use PKCS#1 padding and so you can use
+this S-expression for @var{data}:
@example
(data
@@ -4335,7 +4335,9 @@ data is assumed to be an MPI stored in the format described by
@var{mpifmt} and returned as a standard Libgcrypt MPI. The caller must
release this returned value using @code{gcry_mpi_release}. If there is
no data at the given index, the index represents a list or the value
-can't be converted to an MPI, @code{NULL} is returned.
+can't be converted to an MPI, @code{NULL} is returned. If you use
+this function to parse results of a public key function, you most
+likely want to use @code{GCRYMPI_FMT_USG}.
@end deftypefun