From c082201a36303850e67300e0e8e3e2c67ed914dc Mon Sep 17 00:00:00 2001 From: "Dr. Stephen Henson" Date: Fri, 12 Aug 2016 17:27:11 +0100 Subject: [PATCH] add documentation Reviewed-by: Rich Salz --- doc/apps/genpkey.pod | 7 +++++++ doc/apps/pkeyutl.pod | 5 +++++ 2 files changed, 12 insertions(+) diff --git a/doc/apps/genpkey.pod b/doc/apps/genpkey.pod index 8a789463cd..e77fc7ef4e 100644 --- a/doc/apps/genpkey.pod +++ b/doc/apps/genpkey.pod @@ -192,6 +192,9 @@ numeric OID. Following parameter sets are supported: =back +=head1 X25519 KEY GENERATION OPTIONS + +The X25519 algorithm does not currently support any key generation options. =head1 NOTES @@ -253,6 +256,10 @@ Generate EC key directly: -pkeyopt ec_paramgen_curve:P-384 \ -pkeyopt ec_param_enc:named_curve +Generate an X25519 private key: + + openssl genpkey -algorithm X25519 -out xkey.pem + =head1 HISTORY The ability to use NIST curve names, and to generate an EC key directly, diff --git a/doc/apps/pkeyutl.pod b/doc/apps/pkeyutl.pod index 91eeda5488..8a455b8187 100644 --- a/doc/apps/pkeyutl.pod +++ b/doc/apps/pkeyutl.pod @@ -240,6 +240,11 @@ verify operations use ECDSA and derive uses ECDH. Currently there are no additional options other than B. Only the SHA1 digest can be used and this digest is assumed by default. +=head1 X25519 ALGORITHM + +The X25519 algorithm supports key derivation only. Currently there are no +additional options. + =head1 EXAMPLES Sign some data using a private key: -- 2.25.1