diff options
author | bodo <bodo> | 2007-11-19 07:24:07 +0000 |
---|---|---|
committer | bodo <bodo> | 2007-11-19 07:24:07 +0000 |
commit | 5f603860e96bd0c6fb82a6f858433d5ca7351fc1 (patch) | |
tree | 03fa2bc0243072b494ca712ff1c0f99e41d89173 /doc | |
parent | 418da1c94e07eca51da7e1bf4b4c2482444ed453 (diff) | |
download | openssl-5f603860e96bd0c6fb82a6f858433d5ca7351fc1.tar.gz |
fix typos
Submitted by: Ernst G. Giessmann
Diffstat (limited to 'doc')
-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 724ccfe04..29d151366 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 |