From: Niels Möller <nisse@lysator.liu.se>
Date: Fri, 21 Apr 2006 07:06:07 +0000 (+0200)
Subject: (Public-key algorithms): Say that the public key
X-Git-Tag: head_before_experimental_merge_20060516~9
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1039bd732c5d4477d9caae0c4bfeae95a9990d5c;p=thirdparty%2Fnettle.git

(Public-key algorithms): Say that the public key
operations are undocumented, not unsupported. Reported by Jeronimo
Pellegrini.

Rev: src/nettle/nettle.texinfo:1.33
---

diff --git a/nettle.texinfo b/nettle.texinfo
index 05d16e80..09f7eae4 100644
--- a/nettle.texinfo
+++ b/nettle.texinfo
@@ -1507,9 +1507,9 @@ knows the secret, it is easy to compute both @code{F} and it's inverse.
 If this sounds strange, look at the @acronym{RSA} example below.
 
 Two important uses for one-way functions with trapdoors are public-key
-encryption, and digital signatures. Of these, I won't say more about
-public-key encryption, as that isn't yet supported by Nettle. So the
-rest of this chapter is about digital signatures.
+encryption, and digital signatures. The public-key encryption functions
+in Nettle are not yet documented; the rest of this chapter is about
+digital signatures.
 
 To use a digital signature algorithm, one must first create a
 @dfn{key-pair}: A public key and a corresponding private key. The private