Make all configuration macros available for application by making

sure they are available in opensslconf.h, by giving them names starting
with "OPENSSL_" to avoid conflicts with other packages and by making
sure e_os2.h will cover all platform-specific cases together with
opensslconf.h.

I've checked fairly well that nothing breaks with this (apart from
external software that will adapt if they have used something like
NO_KRB5), but I can't guarantee it completely, so a review of this
change would be a good thing.

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/HOWTO/certificates.txt b/doc/HOWTO/certificates.txt
index 74fe84b..8804864 100644
--- a/doc/HOWTO/certificates.txt
+++ b/doc/HOWTO/certificates.txt
@@ -1,4 +1,4 @@
-[DRAFT!]
+<DRAFT!>
 			HOWTO certificates
 
 How you handle certificates depend a great deal on what your role is.
@@ -14,7 +14,7 @@ Certificate authorities should read ca.txt.
 In all the cases shown below, the standard configuration file, as
 compiled into openssl, will be used.  You may find it in /etc/,
 /usr/local/ssr/ or somewhere else.  The name is openssl.cnf, and
-is better described in another HOWTO [config.txt?].  If you want to
+is better described in another HOWTO <config.txt?>.  If you want to
 use a different configuration file, use the argument '-config {file}'
 with the command shown below.
 
@@ -48,7 +48,7 @@ command 'openssl req' like this:
 Now, cert.csr can be sent to the certificate authority, if they can
 handle files in PEM format.  If not, use the extra argument '-outform'
 followed by the keyword for the format to use (see another HOWTO
-[formats.txt?]).  In some cases, that isn't sufficient and you will
+<formats.txt?>).  In some cases, that isn't sufficient and you will
 have to be more creative.
 
 When the certificate authority has then done the checks the need to
@@ -71,7 +71,7 @@ convert between some (most?) formats.
 So, depending on your application, you may have to convert your
 certificate and your key to various formats, most often also putting
 them together into one file.  The ways to do this is described in
-another HOWTO [formats.txt?], I will just mention the simplest case.
+another HOWTO <formats.txt?>, I will just mention the simplest case.
 In the case of a raw DER thing in PEM format, and assuming that's all
 right for yor applications, simply concatenating the certificate and
 the key into a new file and using that one should be enough.  With