From 15bd07e9233dd01e6d1730400ffa58c540a315cd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bodo=20M=C3=B6ller?= Date: Mon, 19 Nov 2007 07:24:08 +0000 Subject: fix typos Submitted by: Ernst G. Giessmann --- doc/crypto/ASN1_generate_nconf.pod | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) (limited to 'doc') 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 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, @@ -83,13 +87,13 @@ the format B. =item B, B -Emcodes an ASN1 B. B represents the contents +Encodes an ASN1 B. B represents the contents of this structure, the format strings B and B can be used to specify the format of B. -=item B, B +=item B, B -Emcodes an ASN1 B. B represents the contents +Encodes an ASN1 B. B represents the contents of this structure, the format strings B, B and B can be used to specify the format of B. @@ -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 -- cgit v1.2.3