From c9ea4df8f9dcf34933e0763c3907cfdcf93d820e Mon Sep 17 00:00:00 2001
From: "Dr. Stephen Henson" <steve@openssl.org>
Date: Wed, 21 Aug 2013 13:39:27 +0100
Subject: [PATCH] Document -force_pubkey option. (cherry picked from commit
 b093a06866bf632a97a9a0286e2d08f69c3cf7dd)

---
 doc/apps/x509.pod | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/apps/x509.pod b/doc/apps/x509.pod
index d2d9eb812a..19fae07e48 100644
--- a/doc/apps/x509.pod
+++ b/doc/apps/x509.pod
@@ -48,6 +48,7 @@ B<openssl> B<x509>
 [B<-CAkey filename>]
 [B<-CAcreateserial>]
 [B<-CAserial filename>]
+[B<-force_pubkey key>]
 [B<-text>]
 [B<-C>]
 [B<-md2|-md5|-sha1|-mdc2>]
@@ -400,6 +401,15 @@ specified then the extensions should either be contained in the unnamed
 L<x509v3_config(5)|x509v3_config(5)> manual page for details of the
 extension section format.
 
+=item B<-force_pubkey key>
+
+when a certificate is created set its public key to B<key> instead of the
+key in the certificate or certificate request. This option is useful for
+creating certificates where the algorithm can't normally sign requests, for
+example DH.
+
+The format or B<key> can be specified using the B<-keyform> option.
+
 =back
 
 =head2 NAME OPTIONS
-- 
2.25.1