diff options
author | Bodo Möller <bodo@openssl.org> | 2007-11-19 07:24:08 +0000 |
---|---|---|
committer | Bodo Möller <bodo@openssl.org> | 2007-11-19 07:24:08 +0000 |
commit | 15bd07e9233dd01e6d1730400ffa58c540a315cd (patch) | |
tree | e58fb2e4cab919e50667fb17eae908249c986d39 /doc/crypto | |
parent | fdf355878cba2c87cd4d76c5f2efa91d81030cbd (diff) |
fix typos
Submitted by: Ernst G. Giessmann
Diffstat (limited to 'doc/crypto')
-rw-r--r-- | doc/crypto/ASN1_generate_nconf.pod | 22 |
1 files changed, 13 insertions, 9 deletions
diff --git a/doc/crypto/ASN1_generate_nconf.pod b/doc/crypto/ASN1_generate_nconf.pod index 724ccfe040..29d151366d 100644 --- a/doc/crypto/ASN1_generate_nconf.pod +++ b/doc/crypto/ASN1_generate_nconf.pod @@ -30,7 +30,11 @@ The actual data encoded is determined by the string B<str> and the configuration information. The general format of the string is: - B<[modifier,]type[:value]> +=over 2 + +=item B<[modifier,]type[:value]> + +=back That is zero or more comma separated modifiers followed by a type followed by an optional colon and a value. The formats of B<type>, @@ -83,13 +87,13 @@ the format B<YYYYMMDDHHMMSSZ>. =item B<OCTETSTRING>, B<OCT> -Emcodes an ASN1 B<OCTET STRING>. B<value> represents the contents +Encodes an ASN1 B<OCTET STRING>. B<value> represents the contents of this structure, the format strings B<ASCII> and B<HEX> can be used to specify the format of B<value>. -=item B<BITSRING>, B<BITSTR> +=item B<BITSTRING>, B<BITSTR> -Emcodes an ASN1 B<BIT STRING>. B<value> represents the contents +Encodes an ASN1 B<BIT STRING>. B<value> represents the contents of this structure, the format strings B<ASCII>, B<HEX> and B<BITLIST> can be used to specify the format of B<value>. @@ -174,13 +178,13 @@ An IA5String explicitly tagged using APPLICATION tagging: A more complex example using a config file to produce a SEQUENCE consiting of a BOOL an OID and a UTF8String: -asn1 = SEQUENCE:seq_section + asn1 = SEQUENCE:seq_section -[seq_section] + [seq_section] -field1 = BOOLEAN:TRUE -field2 = OID:commonName -field3 = UTF8:Third field + field1 = BOOLEAN:TRUE + field2 = OID:commonName + field3 = UTF8:Third field This example produces an RSAPrivateKey structure, this is the key contained in the file client.pem in all OpenSSL distributions |