From: Lutz Jänicke <jaenicke@openssl.org>
Date: Thu, 14 Nov 2002 11:13:01 +0000 (+0000)
Subject: Don't declare 2 WARNINGS sections
X-Git-Tag: OpenSSL_0_9_7-beta4~18^2~29
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=1f30946481f460d68345460f1280af6e0b1d27cd;p=oweals%2Fopenssl.git

Don't declare 2 WARNINGS sections
Submitted by:
Reviewed by:
PR:
---

diff --git a/doc/apps/ca.pod b/doc/apps/ca.pod
index f50fe9c8ed..183cd475c8 100644
--- a/doc/apps/ca.pod
+++ b/doc/apps/ca.pod
@@ -517,18 +517,6 @@ A sample configuration file with the relevant sections for B<ca>:
  commonName             = supplied
  emailAddress           = optional
 
-=head1 WARNINGS
-
-The B<ca> command is quirky and at times downright unfriendly.
-
-The B<ca> utility was originally meant as an example of how to do things
-in a CA. It was not supposed to be used as a full blown CA itself:
-nevertheless some people are using it for this purpose.
-
-The B<ca> command is effectively a single user command: no locking is
-done on the various files and attempts to run more than one B<ca> command
-on the same database can have unpredictable results.
-
 =head1 FILES
 
 Note: the location of all files can change either by compile time options,
@@ -593,6 +581,16 @@ create an empty file.
 
 =head1 WARNINGS
 
+The B<ca> command is quirky and at times downright unfriendly.
+
+The B<ca> utility was originally meant as an example of how to do things
+in a CA. It was not supposed to be used as a full blown CA itself:
+nevertheless some people are using it for this purpose.
+
+The B<ca> command is effectively a single user command: no locking is
+done on the various files and attempts to run more than one B<ca> command
+on the same database can have unpredictable results.
+
 The B<copy_extensions> option should be used with caution. If care is
 not taken then it can be a security risk. For example if a certificate
 request contains a basicConstraints extension with CA:TRUE and the