Commit 9b86974e authored by Rich Salz's avatar Rich Salz Committed by Rich Salz
Browse files

Fix L<> content in manpages 



L<foo|foo> is sub-optimal  If the xref is the same as the title,
which is what we do, then you only need L<foo>.  This fixes all
1457 occurrences in 349 files.  Approximately.  (And pod used to
need both.)

Reviewed-by: default avatarRichard Levitte <levitte@openssl.org>
parent 3da9505d

doc/apps/CA.pl.pod

+3 −3
Original line number Original line Diff line number Diff line
@@ -128,7 +128,7 @@ the request and finally create a PKCS#12 file containing it. 
=head1 DSA CERTIFICATES

=head1 DSA CERTIFICATES





Although the B<CA.pl> creates RSA CAs and requests it is still possible to

Although the B<CA.pl> creates RSA CAs and requests it is still possible to

use it with DSA certificates and requests using the L<req(1)|req(1)> command

use it with DSA certificates and requests using the L<req(1)> command

directly. The following example shows the steps that would typically be taken.

directly. The following example shows the steps that would typically be taken.





Create some DSA parameters:

Create some DSA parameters:
@@ -184,7 +184,7 @@ configuration file, not just its directory. 




=head1 SEE ALSO

=head1 SEE ALSO





L<x509(1)|x509(1)>, L<ca(1)|ca(1)>, L<req(1)|req(1)>, L<pkcs12(1)|pkcs12(1)>,

L<x509(1)>, L<ca(1)>, L<req(1)>, L<pkcs12(1)>,

L<config(5)|config(5)>

L<config(5)>





=cut
 
=cut

doc/apps/asn1parse.pod

+2 −2
Original line number Original line Diff line number Diff line
@@ -83,7 +83,7 @@ option can be used multiple times to "drill down" into a nested structure. 
=item B<-genstr string>, B<-genconf file>

=item B<-genstr string>, B<-genconf file>





generate encoded data based on B<string>, B<file> or both using

generate encoded data based on B<string>, B<file> or both using

L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. If B<file> only is

L<ASN1_generate_nconf(3)> format. If B<file> only is

present then the string is obtained from the default section using the name

present then the string is obtained from the default section using the name

B<asn1>. The encoded data is passed through the ASN1 parser and printed out as

B<asn1>. The encoded data is passed through the ASN1 parser and printed out as

though it came from a file, the contents can thus be examined and written to a

though it came from a file, the contents can thus be examined and written to a
@@ -189,6 +189,6 @@ ASN.1 types is not well handled (if at all). 




=head1 SEE ALSO

=head1 SEE ALSO





L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)>

L<ASN1_generate_nconf(3)>





=cut
 
=cut

doc/apps/c_rehash.pod

+3 −3
Original line number Original line Diff line number Diff line
@@ -109,6 +109,6 @@ Ignored if directories are listed on the command line. 




=head1 SEE ALSO

=head1 SEE ALSO





L<openssl(1)|openssl(1)>,

L<openssl(1)>,

L<crl(1)|crl(1)>.

L<crl(1)>.

L<x509(1)|x509(1)>.
 
L<x509(1)>.

doc/apps/ca.pod

+6 −6
Original line number Original line Diff line number Diff line
@@ -141,7 +141,7 @@ self-signed certificate. 
=item B<-passin arg>

=item B<-passin arg>





the key password source. For more information about the format of B<arg>

the key password source. For more information about the format of B<arg>

see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)|openssl(1)>.

see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)>.





=item B<-verbose>

=item B<-verbose>
@@ -214,7 +214,7 @@ to be added when a certificate is issued (defaults to B<x509_extensions> 
unless the B<-extfile> option is used). If no extension section is

unless the B<-extfile> option is used). If no extension section is

present then, a V1 certificate is created. If the extension section

present then, a V1 certificate is created. If the extension section

is present (even if it is empty), then a V3 certificate is created. See the:w

is present (even if it is empty), then a V3 certificate is created. See the:w

L<x509v3_config(5)|x509v3_config(5)> manual page for details of the

L<x509v3_config(5)> manual page for details of the

extension section format.

extension section format.





=item B<-extfile file>

=item B<-extfile file>
@@ -319,7 +319,7 @@ created, if the CRL extension section is present (even if it is 
empty) then a V2 CRL is created. The CRL extensions specified are

empty) then a V2 CRL is created. The CRL extensions specified are

CRL extensions and B<not> CRL entry extensions.  It should be noted

CRL extensions and B<not> CRL entry extensions.  It should be noted

that some software (for example Netscape) can't handle V2 CRLs. See

that some software (for example Netscape) can't handle V2 CRLs. See

L<x509v3_config(5)|x509v3_config(5)> manual page for details of the

L<x509v3_config(5)> manual page for details of the

extension section format.

extension section format.





=back

=back
@@ -380,7 +380,7 @@ CA private key. Mandatory. 
=item B<RANDFILE>

=item B<RANDFILE>





a file used to read and write random number seed information, or

a file used to read and write random number seed information, or

an EGD socket (see L<RAND_egd(3)|RAND_egd(3)>).

an EGD socket (see L<RAND_egd(3)>).





=item B<default_days>

=item B<default_days>
@@ -690,7 +690,7 @@ then even if a certificate is issued with CA:TRUE it will not be valid. 




=head1 SEE ALSO

=head1 SEE ALSO





L<req(1)|req(1)>, L<spkac(1)|spkac(1)>, L<x509(1)|x509(1)>, L<CA.pl(1)|CA.pl(1)>,

L<req(1)>, L<spkac(1)>, L<x509(1)>, L<CA.pl(1)>,

L<config(5)|config(5)>, L<x509v3_config(5)|x509v3_config(5)> 

L<config(5)>, L<x509v3_config(5)> 





=cut
 
=cut

doc/apps/ciphers.pod

+1 −1
Original line number Original line Diff line number Diff line
@@ -721,7 +721,7 @@ Set security level to 2 and display all ciphers consistent with level 2: 




=head1 SEE ALSO

=head1 SEE ALSO





L<s_client(1)|s_client(1)>, L<s_server(1)|s_server(1)>, L<ssl(3)|ssl(3)>

L<s_client(1)>, L<s_server(1)>, L<ssl(3)>





=head1 HISTORY

=head1 HISTORY