Remove SSLeay history, etc., from docs If something was "present in all versions" of SSLeay, or if it was added to a version of SSLeay (and therefore predates OpenSSL), remove mention of it. Documentation history now starts with OpenSSL. Remove mention of all history before OpenSSL 0.9.8, inclusive. Remove all AUTHOR sections. Reviewed-by: Tim Hudson <tjh@openssl.org>
diff --git a/doc/apps/ciphers.pod b/doc/apps/ciphers.pod index 7598276..389b07c 100644 --- a/doc/apps/ciphers.pod +++ b/doc/apps/ciphers.pod
@@ -162,9 +162,7 @@ =item B<EXPORT56> -56 bit export encryption algorithms. In OpenSSL 0.9.8c and later the set of -56 bit export ciphers is empty unless OpenSSL has been explicitly configured -with support for experimental ciphers. +56 bit export encryption algorithms. This list is empty. =item B<eNULL>, B<NULL> @@ -726,8 +724,6 @@ =head1 HISTORY -The B<COMPLENTOFALL> and B<COMPLEMENTOFDEFAULT> selection options -for cipherlist strings were added in OpenSSL 0.9.7. The B<-V> option for the B<ciphers> command was added in OpenSSL 1.0.0. =cut
diff --git a/doc/apps/config.pod b/doc/apps/config.pod index 22bb6c5..e238e15 100644 --- a/doc/apps/config.pod +++ b/doc/apps/config.pod
@@ -56,7 +56,7 @@ =head1 OPENSSL LIBRARY CONFIGURATION -In OpenSSL 0.9.7 and later applications can automatically configure certain +Applications can automatically configure certain aspects of OpenSSL using the master OpenSSL configuration file, or optionally an alternative configuration file. The B<openssl> utility includes this functionality: any sub command uses the master OpenSSL configuration file @@ -106,7 +106,7 @@ some_new_oid = 1.2.3.4 some_other_oid = 1.2.3.5 -In OpenSSL 0.9.8 it is also possible to set the value to the long name followed +It is also possible to set the value to the long name followed by a comma and the numerical OID form. For example: shortName = some object long name, 1.2.3.4
diff --git a/doc/apps/dhparam.pod b/doc/apps/dhparam.pod index 8bb196d..b0a9802 100644 --- a/doc/apps/dhparam.pod +++ b/doc/apps/dhparam.pod
@@ -141,9 +141,4 @@ L<dsaparam(1)> -=head1 HISTORY - -The B<dhparam> command was added in OpenSSL 0.9.5. -The B<-dsaparam> option was added in OpenSSL 0.9.6. - =cut
diff --git a/doc/apps/ec.pod b/doc/apps/ec.pod index ebc49ea..379d0a8 100644 --- a/doc/apps/ec.pod +++ b/doc/apps/ec.pod
@@ -179,12 +179,4 @@ L<ecparam(1)>, L<dsa(1)>, L<rsa(1)> -=head1 HISTORY - -The ec command was first introduced in OpenSSL 0.9.8. - -=head1 AUTHOR - -Nils Larsch for the OpenSSL project (http://www.openssl.org). - =cut
diff --git a/doc/apps/ecparam.pod b/doc/apps/ecparam.pod index bfb155a..56962ab 100644 --- a/doc/apps/ecparam.pod +++ b/doc/apps/ecparam.pod
@@ -168,12 +168,4 @@ L<ec(1)>, L<dsaparam(1)> -=head1 HISTORY - -The ecparam command was first introduced in OpenSSL 0.9.8. - -=head1 AUTHOR - -Nils Larsch for the OpenSSL project (http://www.openssl.org) - =cut
diff --git a/doc/apps/genpkey.pod b/doc/apps/genpkey.pod index d574caa..dee9722 100644 --- a/doc/apps/genpkey.pod +++ b/doc/apps/genpkey.pod
@@ -141,7 +141,7 @@ =head1 EC PARAMETER GENERATION OPTIONS -In OpenSSL 1.0.2 and later the EC parameter generation options below can also +The EC parameter generation options below can also be supplied as EC key generation options. This can (for example) generate a key from a named curve without the need to use an explicit parameter file. @@ -149,8 +149,7 @@ =item B<ec_paramgen_curve:curve> -the EC curve to use. OpenSSL 1.0.2 and later supports NIST curve names -such as "P-256". +the EC curve to use. OpenSSL supports NIST curve names such as "P-256". =item B<ec_param_enc:encoding> @@ -243,11 +242,16 @@ openssl genpkey -paramfile ecp.pem -out eckey.pem -Generate EC key directly (OpenSSL 1.0.2+ only): +Generate EC key directly: openssl genpkey -algorithm EC -out eckey.pem \ -pkeyopt ec_paramgen_curve:P-384 \ -pkeyopt ec_param_enc:named_curve +=head1 HISTORY + +The ability to use NIST curve names, and to generate an EC key directly, +were added in OpenSSL 1.0.2. + =cut
diff --git a/doc/apps/openssl.pod b/doc/apps/openssl.pod index 30ea9bd..f148404 100644 --- a/doc/apps/openssl.pod +++ b/doc/apps/openssl.pod
@@ -412,10 +412,7 @@ =head1 HISTORY -The openssl(1) document appeared in OpenSSL 0.9.2. -The B<list->I<XXX>B<-commands> pseudo-commands were added in OpenSSL 0.9.3; The B<list->I<XXX>B<-algorithms> pseudo-commands were added in OpenSSL 1.0.0; -the B<no->I<XXX> pseudo-commands were added in OpenSSL 0.9.5a. For notes on the availability of other commands, see their individual manual pages.
diff --git a/doc/apps/pkcs12.pod b/doc/apps/pkcs12.pod index f8162d0..811b822 100644 --- a/doc/apps/pkcs12.pod +++ b/doc/apps/pkcs12.pod
@@ -348,30 +348,6 @@ openssl pkcs12 -export -in file.pem -out file.p12 -name "My Certificate" \ -certfile othercerts.pem -=head1 BUGS - -Some would argue that the PKCS#12 standard is one big bug :-) - -Versions of OpenSSL before 0.9.6a had a bug in the PKCS#12 key generation -routines. Under rare circumstances this could produce a PKCS#12 file encrypted -with an invalid key. As a result some PKCS#12 files which triggered this bug -from other implementations (MSIE or Netscape) could not be decrypted -by OpenSSL and similarly OpenSSL could produce PKCS#12 files which could -not be decrypted by other implementations. The chances of producing such -a file are relatively small: less than 1 in 256. - -A side effect of fixing this bug is that any old invalidly encrypted PKCS#12 -files cannot no longer be parsed by the fixed version. Under such circumstances -the B<pkcs12> utility will report that the MAC is OK but fail with a decryption -error when extracting private keys. - -This problem can be resolved by extracting the private keys and certificates -from the PKCS#12 file using an older version of OpenSSL and recreating the PKCS#12 -file from the keys and certificates using a newer version of OpenSSL. For example: - - old-openssl -in bad.p12 -out keycerts.pem - openssl -in keycerts.pem -export -name "My PKCS#12 file" -out fixed.p12 - =head1 SEE ALSO L<pkcs8(1)>
diff --git a/doc/apps/ts.pod b/doc/apps/ts.pod index 7a55b61..e2b555a 100644 --- a/doc/apps/ts.pod +++ b/doc/apps/ts.pod
@@ -581,10 +581,6 @@ =cut -=head1 AUTHOR - -Zoltan Glozik <zglozik@opentsa.org>, OpenTSA project (http://www.opentsa.org) - =head1 SEE ALSO L<tsget(1)>, L<openssl(1)>, L<req(1)>,
diff --git a/doc/apps/tsget.pod b/doc/apps/tsget.pod index 3452c63..34187eb 100644 --- a/doc/apps/tsget.pod +++ b/doc/apps/tsget.pod
@@ -182,10 +182,6 @@ export TSGET tsget file1.tsq -=head1 AUTHOR - -Zoltan Glozik <zglozik@opentsa.org>, OpenTSA project (http://www.opentsa.org) - =head1 SEE ALSO L<openssl(1)>, L<ts(1)>, L<curl(1)>,
diff --git a/doc/apps/verify.pod b/doc/apps/verify.pod index afd1b95..c935269 100644 --- a/doc/apps/verify.pod +++ b/doc/apps/verify.pod
@@ -283,9 +283,8 @@ to be the root CA. The process of 'looking up the issuers certificate' itself involves a number -of steps. In versions of OpenSSL before 0.9.5a the first certificate whose -subject name matched the issuer of the current certificate was assumed to be -the issuers certificate. In OpenSSL 0.9.6 and later all certificates +of steps. +Ater all certificates whose subject name matches the issuer name of the current certificate are subject to further tests. The relevant authority key identifier components of the current certificate (if present) must match the subject key identifier
diff --git a/doc/apps/version.pod b/doc/apps/version.pod index 58f543b..61a364b 100644 --- a/doc/apps/version.pod +++ b/doc/apps/version.pod
@@ -58,8 +58,4 @@ The output of B<openssl version -a> would typically be used when sending in a bug report. -=head1 HISTORY - -The B<-d> option was added in OpenSSL 0.9.7. - =cut
diff --git a/doc/apps/x509.pod b/doc/apps/x509.pod index d4790605..1c98e9d 100644 --- a/doc/apps/x509.pod +++ b/doc/apps/x509.pod
@@ -869,11 +869,6 @@ There should be options to explicitly set such things as start and end dates rather than an offset from the current time. -The code to implement the verify behaviour described in the B<TRUST SETTINGS> -is currently being developed. It thus describes the intended behaviour rather -than the current behaviour. It is hoped that it will represent reality in -OpenSSL 0.9.5 and later. - =head1 SEE ALSO L<req(1)>, L<ca(1)>, L<genrsa(1)>, @@ -882,8 +877,6 @@ =head1 HISTORY -Before OpenSSL 0.9.8, the default digest for RSA keys was MD5. - The hash algorithm used in the B<-subject_hash> and B<-issuer_hash> options before OpenSSL 1.0.0 was based on the deprecated MD5 algorithm and the encoding of the distinguished name. In OpenSSL 1.0.0 and later it is based on a
diff --git a/doc/apps/x509v3_config.pod b/doc/apps/x509v3_config.pod index 297cbaa..e965be6 100644 --- a/doc/apps/x509v3_config.pod +++ b/doc/apps/x509v3_config.pod
@@ -508,16 +508,6 @@ email.1=steve@here email.2=steve@there -=head1 HISTORY - -The X509v3 extension code was first added to OpenSSL 0.9.2. - -Policy mappings, inhibit any policy and name constraints support was added in -OpenSSL 0.9.8 - -The B<directoryName> and B<otherName> option as well as the B<ASN1> option -for arbitrary extensions was added in OpenSSL 0.9.8 - =head1 SEE ALSO L<req(1)>, L<ca(1)>, L<x509(1)>,