From 084adb601f2d375395c6cdcedf8af91f1065fe4e Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Mon, 9 Oct 2006 16:22:20 +0000 Subject: Feh, wrong vendor branch merge proceedure, clean up before trying again. svn path=/openssl/vendor/0.9.8d; revision=374 --- .../0.9.8d/doc/crypto/ASN1_generate_nconf.pod | 253 --------------------- 1 file changed, 253 deletions(-) delete mode 100644 openssl/vendor/0.9.8d/doc/crypto/ASN1_generate_nconf.pod (limited to 'openssl/vendor/0.9.8d/doc/crypto/ASN1_generate_nconf.pod') diff --git a/openssl/vendor/0.9.8d/doc/crypto/ASN1_generate_nconf.pod b/openssl/vendor/0.9.8d/doc/crypto/ASN1_generate_nconf.pod deleted file mode 100644 index ba6e3c2e..00000000 --- a/openssl/vendor/0.9.8d/doc/crypto/ASN1_generate_nconf.pod +++ /dev/null @@ -1,253 +0,0 @@ -=pod - -=head1 NAME - -ASN1_generate_nconf, ASN1_generate_v3 - ASN1 generation functions - -=head1 SYNOPSIS - - ASN1_TYPE *ASN1_generate_nconf(char *str, CONF *nconf); - ASN1_TYPE *ASN1_generate_v3(char *str, X509V3_CTX *cnf); - -=head1 DESCRIPTION - -These functions generate the ASN1 encoding of a string -in an B structure. - -B contains the string to encode B or B contains -the optional configuration information where additional strings -will be read from. B will typically come from a config -file wherease B is obtained from an B structure -which will typically be used by X509 v3 certificate extension -functions. B or B can be set to B if no additional -configuration will be used. - -=head1 GENERATION STRING FORMAT - -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]> - -That is zero or more comma separated modifiers followed by a type -followed by an optional colon and a value. The formats of B, -B and B are explained below. - -=head2 SUPPORTED TYPES - -The supported types are listed below. Unless otherwise specified -only the B format is permissible. - -=over 2 - -=item B, B - -This encodes a boolean type. The B string is mandatory and -should be B or B. Additionally B, B, B, -B, B, B, B, B, B, B, B and B -are acceptable. - -=item B - -Encode the B type, the B string must not be present. - -=item B, B - -Encodes an ASN1 B type. The B string represents -the value of the integer, it can be preceeded by a minus sign and -is normally interpreted as a decimal value unless the prefix B<0x> -is included. - -=item B, B - -Encodes the ASN1 B type, it is otherwise identical to -B. - -=item B, B - -Encodes an ASN1 B, the B string can be -a short name, a long name or numerical format. - -=item B, B - -Encodes an ASN1 B structure, the value should be in -the format B. - -=item B, B - -Encodes an ASN1 B structure, the value should be in -the format B. - -=item B, B - -Emcodes 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 - -Emcodes 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. - -If the format is anything other than B the number of unused -bits is set to zero. - -=item B, B, B, B, B, -B, B, B, B, -B, B, B, B, -B, B, B - -These encode the corresponding string types. B represents the -contents of this structure. The format can be B or B. - -=item B, B, B - -Formats the result as an ASN1 B or B type. B -should be a section name which will contain the contents. The -field names in the section are ignored and the values are in the -generated string format. If B is absent then an empty SEQUENCE -will be encoded. - -=back - -=head2 MODIFIERS - -Modifiers affect the following structure, they can be used to -add EXPLICIT or IMPLICIT tagging, add wrappers or to change -the string format of the final type and value. The supported -formats are documented below. - -=over 2 - -=item B, B - -Add an explicit tag to the following structure. This string -should be followed by a colon and the tag value to use as a -decimal value. - -By following the number with B, B, B

or B UNIVERSAL, -APPLICATION, PRIVATE or CONTEXT SPECIFIC tagging can be used, -the default is CONTEXT SPECIFIC. - -=item B, B - -This is the same as B except IMPLICIT tagging is used -instead. - -=item B, B, B, B - -The following structure is surrounded by an OCTET STRING, a SEQUENCE, -a SET or a BIT STRING respectively. For a BIT STRING the number of unused -bits is set to zero. - -=item B - -This specifies the format of the ultimate value. It should be followed -by a colon and one of the strings B, B, B or B. - -If no format specifier is included then B is used. If B is specified -then the value string must be a valid B string. For B the output must -be a set of hex digits. B (which is only valid for a BIT STRING) is a -comma separated list of set bits. - -=back - -=head1 EXAMPLES - -A simple IA5String: - - IA5STRING:Hello World - -An IA5String explicitly tagged: - - EXPLICIT:0,IA5STRING:Hello World - -An IA5String explicitly tagged using APPLICATION tagging: - - EXPLICIT:0A,IA5STRING:Hello World - -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 - -[seq_section] - -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 -(note: the field names such as 'coeff' are ignored and are present just -for clarity): - - asn1=SEQUENCE:private_key - [private_key] - version=INTEGER:0 - - n=INTEGER:0xBB6FE79432CC6EA2D8F970675A5A87BFBE1AFF0BE63E879F2AFFB93644\ - D4D2C6D000430DEC66ABF47829E74B8C5108623A1C0EE8BE217B3AD8D36D5EB4FCA1D9 - - e=INTEGER:0x010001 - - d=INTEGER:0x6F05EAD2F27FFAEC84BEC360C4B928FD5F3A9865D0FCAAD291E2A52F4A\ - F810DC6373278C006A0ABBA27DC8C63BF97F7E666E27C5284D7D3B1FFFE16B7A87B51D - - p=INTEGER:0xF3929B9435608F8A22C208D86795271D54EBDFB09DDEF539AB083DA912\ - D4BD57 - - q=INTEGER:0xC50016F89DFF2561347ED1186A46E150E28BF2D0F539A1594BBD7FE467\ - 46EC4F - - exp1=INTEGER:0x9E7D4326C924AFC1DEA40B45650134966D6F9DFA3A7F9D698CD4ABEA\ - 9C0A39B9 - - exp2=INTEGER:0xBA84003BB95355AFB7C50DF140C60513D0BA51D637272E355E397779\ - E7B2458F - - coeff=INTEGER:0x30B9E4F2AFA5AC679F920FC83F1F2DF1BAF1779CF989447FABC2F5\ - 628657053A - -This example is the corresponding public key in a SubjectPublicKeyInfo -structure: - - # Start with a SEQUENCE - asn1=SEQUENCE:pubkeyinfo - - # pubkeyinfo contains an algorithm identifier and the public key wrapped - # in a BIT STRING - [pubkeyinfo] - algorithm=SEQUENCE:rsa_alg - pubkey=BITWRAP,SEQUENCE:rsapubkey - - # algorithm ID for RSA is just an OID and a NULL - [rsa_alg] - algorithm=OID:rsaEncryption - parameter=NULL - - # Actual public key: modulus and exponent - [rsapubkey] - n=INTEGER:0xBB6FE79432CC6EA2D8F970675A5A87BFBE1AFF0BE63E879F2AFFB93644\ - D4D2C6D000430DEC66ABF47829E74B8C5108623A1C0EE8BE217B3AD8D36D5EB4FCA1D9 - - e=INTEGER:0x010001 - -=head1 RETURN VALUES - -ASN1_generate_nconf() and ASN1_generate_v3() return the encoded -data as an B structure or B if an error occurred. - -The error codes that can be obtained by L. - -=head1 SEE ALSO - -L - -=head1 HISTORY - -ASN1_generate_nconf() and ASN1_generate_v3() were added to OpenSSL 0.9.8 - -=cut -- cgit v1.2.3