generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix link for ASN1_generate_nconf

Browse Source
This commit is contained in:
Dr. Stephen Henson 2006-11-07 13:44:03 +00:00
parent ff1b10dca1
commit 51cc37b69d
2 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/apps/asn1parse.pod
View File

@ -72,11 +72,11 @@ 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
ASN1_generate_nconf() format. If B<file> only is present then the string L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. If B<file> only is
is obtained from the default section using the name B<asn1>. The encoded present then the string is obtained from the default section using the name
data is passed through the ASN1 parser and printed out as though it came B<asn1>. The encoded data is passed through the ASN1 parser and printed out as
from a file, the contents can thus be examined and written to a file though it came from a file, the contents can thus be examined and written to a
using the B<out> option. file using the B<out> option.
=back =back
@ -168,4 +168,8 @@ Example config file:
There should be options to change the format of output lines. The output of some There should be options to change the format of output lines. The output of some
ASN.1 types is not well handled (if at all). ASN.1 types is not well handled (if at all).
=head1 SEE ALSO
L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)>
=cut =cut

7
doc/apps/x509v3_config.pod
View File

@ -178,7 +178,7 @@ preceeding the name with a B<+> character.
otherName can include arbitrary data associated with an OID: the value otherName can include arbitrary data associated with an OID: the value
should be the OID followed by a semicolon and the content in standard 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: Examples:
@ -441,7 +441,8 @@ the data is formatted correctly for the given extension type.
There are two ways to encode arbitrary extensions. There are two ways to encode arbitrary extensions.
The first way is to use the word ASN1 followed by the extension content 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 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 =head1 SEE ALSO
L<req(1)|req(1)>, L<ca(1)|ca(1)>, L<x509(1)|x509(1)>, 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 =cut