diff options
| author | Dr. Stephen Henson <steve@openssl.org> | 2006-11-07 13:44:03 +0000 |
|---|---|---|
| committer | Dr. Stephen Henson <steve@openssl.org> | 2006-11-07 13:44:03 +0000 |
| commit | 51cc37b69da13c33930585d3d22c020110c98c9f (patch) | |
| tree | 2ba20658d638fc8c73834f8db98e62818e7cde1c /doc/apps/x509v3_config.pod | |
| parent | ff1b10dca131e594d2753f8c4ac10bd7b776303f (diff) | |
Fix link for ASN1_generate_nconf
Diffstat (limited to 'doc/apps/x509v3_config.pod')
| -rw-r--r-- | doc/apps/x509v3_config.pod | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/apps/x509v3_config.pod b/doc/apps/x509v3_config.pod index ac735d6f19..0450067cf1 100644 --- a/doc/apps/x509v3_config.pod +++ b/doc/apps/x509v3_config.pod @@ -178,7 +178,7 @@ preceeding the name with a B<+> character. otherName can include arbitrary data associated with an OID: the value should be the OID followed by a semicolon and the content in standard -L<ASN1_generate_nconf(1)|ASN1_generate_nconf(1)> format. +L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. Examples: @@ -441,7 +441,8 @@ the data is formatted correctly for the given extension type. There are two ways to encode arbitrary extensions. The first way is to use the word ASN1 followed by the extension content -using the same syntax as ASN1_generate_nconf(). For example: +using the same syntax as L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)>. +For example: 1.2.3.4=critical,ASN1:UTF8String:Some random data @@ -522,7 +523,7 @@ for arbitrary extensions was added in OpenSSL 0.9.8 =head1 SEE ALSO L<req(1)|req(1)>, L<ca(1)|ca(1)>, L<x509(1)|x509(1)>, -L<ASN1_generate_nconf(1)|ASN1_generate_nconf(1)> +L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> =cut |