1*0Sstevel@tonic-gate /* crypto/asn1/x_req.c */
2*0Sstevel@tonic-gate /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
3*0Sstevel@tonic-gate * All rights reserved.
4*0Sstevel@tonic-gate *
5*0Sstevel@tonic-gate * This package is an SSL implementation written
6*0Sstevel@tonic-gate * by Eric Young (eay@cryptsoft.com).
7*0Sstevel@tonic-gate * The implementation was written so as to conform with Netscapes SSL.
8*0Sstevel@tonic-gate *
9*0Sstevel@tonic-gate * This library is free for commercial and non-commercial use as long as
10*0Sstevel@tonic-gate * the following conditions are aheared to. The following conditions
11*0Sstevel@tonic-gate * apply to all code found in this distribution, be it the RC4, RSA,
12*0Sstevel@tonic-gate * lhash, DES, etc., code; not just the SSL code. The SSL documentation
13*0Sstevel@tonic-gate * included with this distribution is covered by the same copyright terms
14*0Sstevel@tonic-gate * except that the holder is Tim Hudson (tjh@cryptsoft.com).
15*0Sstevel@tonic-gate *
16*0Sstevel@tonic-gate * Copyright remains Eric Young's, and as such any Copyright notices in
17*0Sstevel@tonic-gate * the code are not to be removed.
18*0Sstevel@tonic-gate * If this package is used in a product, Eric Young should be given attribution
19*0Sstevel@tonic-gate * as the author of the parts of the library used.
20*0Sstevel@tonic-gate * This can be in the form of a textual message at program startup or
21*0Sstevel@tonic-gate * in documentation (online or textual) provided with the package.
22*0Sstevel@tonic-gate *
23*0Sstevel@tonic-gate * Redistribution and use in source and binary forms, with or without
24*0Sstevel@tonic-gate * modification, are permitted provided that the following conditions
25*0Sstevel@tonic-gate * are met:
26*0Sstevel@tonic-gate * 1. Redistributions of source code must retain the copyright
27*0Sstevel@tonic-gate * notice, this list of conditions and the following disclaimer.
28*0Sstevel@tonic-gate * 2. Redistributions in binary form must reproduce the above copyright
29*0Sstevel@tonic-gate * notice, this list of conditions and the following disclaimer in the
30*0Sstevel@tonic-gate * documentation and/or other materials provided with the distribution.
31*0Sstevel@tonic-gate * 3. All advertising materials mentioning features or use of this software
32*0Sstevel@tonic-gate * must display the following acknowledgement:
33*0Sstevel@tonic-gate * "This product includes cryptographic software written by
34*0Sstevel@tonic-gate * Eric Young (eay@cryptsoft.com)"
35*0Sstevel@tonic-gate * The word 'cryptographic' can be left out if the rouines from the library
36*0Sstevel@tonic-gate * being used are not cryptographic related :-).
37*0Sstevel@tonic-gate * 4. If you include any Windows specific code (or a derivative thereof) from
38*0Sstevel@tonic-gate * the apps directory (application code) you must include an acknowledgement:
39*0Sstevel@tonic-gate * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
40*0Sstevel@tonic-gate *
41*0Sstevel@tonic-gate * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
42*0Sstevel@tonic-gate * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
43*0Sstevel@tonic-gate * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
44*0Sstevel@tonic-gate * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
45*0Sstevel@tonic-gate * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
46*0Sstevel@tonic-gate * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
47*0Sstevel@tonic-gate * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
48*0Sstevel@tonic-gate * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
49*0Sstevel@tonic-gate * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
50*0Sstevel@tonic-gate * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
51*0Sstevel@tonic-gate * SUCH DAMAGE.
52*0Sstevel@tonic-gate *
53*0Sstevel@tonic-gate * The licence and distribution terms for any publically available version or
54*0Sstevel@tonic-gate * derivative of this code cannot be changed. i.e. this code cannot simply be
55*0Sstevel@tonic-gate * copied and put under another distribution licence
56*0Sstevel@tonic-gate * [including the GNU Public Licence.]
57*0Sstevel@tonic-gate */
58*0Sstevel@tonic-gate
59*0Sstevel@tonic-gate #include <stdio.h>
60*0Sstevel@tonic-gate #include "cryptlib.h"
61*0Sstevel@tonic-gate #include <openssl/asn1t.h>
62*0Sstevel@tonic-gate #include <openssl/x509.h>
63*0Sstevel@tonic-gate
64*0Sstevel@tonic-gate /* X509_REQ_INFO is handled in an unusual way to get round
65*0Sstevel@tonic-gate * invalid encodings. Some broken certificate requests don't
66*0Sstevel@tonic-gate * encode the attributes field if it is empty. This is in
67*0Sstevel@tonic-gate * violation of PKCS#10 but we need to tolerate it. We do
68*0Sstevel@tonic-gate * this by making the attributes field OPTIONAL then using
69*0Sstevel@tonic-gate * the callback to initialise it to an empty STACK.
70*0Sstevel@tonic-gate *
71*0Sstevel@tonic-gate * This means that the field will be correctly encoded unless
72*0Sstevel@tonic-gate * we NULL out the field.
73*0Sstevel@tonic-gate *
74*0Sstevel@tonic-gate * As a result we no longer need the req_kludge field because
75*0Sstevel@tonic-gate * the information is now contained in the attributes field:
76*0Sstevel@tonic-gate * 1. If it is NULL then it's the invalid omission.
77*0Sstevel@tonic-gate * 2. If it is empty it is the correct encoding.
78*0Sstevel@tonic-gate * 3. If it is not empty then some attributes are present.
79*0Sstevel@tonic-gate *
80*0Sstevel@tonic-gate */
81*0Sstevel@tonic-gate
rinf_cb(int operation,ASN1_VALUE ** pval,const ASN1_ITEM * it)82*0Sstevel@tonic-gate static int rinf_cb(int operation, ASN1_VALUE **pval, const ASN1_ITEM *it)
83*0Sstevel@tonic-gate {
84*0Sstevel@tonic-gate X509_REQ_INFO *rinf = (X509_REQ_INFO *)*pval;
85*0Sstevel@tonic-gate
86*0Sstevel@tonic-gate if(operation == ASN1_OP_NEW_POST) {
87*0Sstevel@tonic-gate rinf->attributes = sk_X509_ATTRIBUTE_new_null();
88*0Sstevel@tonic-gate if(!rinf->attributes) return 0;
89*0Sstevel@tonic-gate }
90*0Sstevel@tonic-gate return 1;
91*0Sstevel@tonic-gate }
92*0Sstevel@tonic-gate
93*0Sstevel@tonic-gate ASN1_SEQUENCE_enc(X509_REQ_INFO, enc, rinf_cb) = {
94*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ_INFO, version, ASN1_INTEGER),
95*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ_INFO, subject, X509_NAME),
96*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ_INFO, pubkey, X509_PUBKEY),
97*0Sstevel@tonic-gate /* This isn't really OPTIONAL but it gets round invalid
98*0Sstevel@tonic-gate * encodings
99*0Sstevel@tonic-gate */
100*0Sstevel@tonic-gate ASN1_IMP_SET_OF_OPT(X509_REQ_INFO, attributes, X509_ATTRIBUTE, 0)
101*0Sstevel@tonic-gate } ASN1_SEQUENCE_END_enc(X509_REQ_INFO, X509_REQ_INFO)
102*0Sstevel@tonic-gate
103*0Sstevel@tonic-gate IMPLEMENT_ASN1_FUNCTIONS(X509_REQ_INFO)
104*0Sstevel@tonic-gate
105*0Sstevel@tonic-gate ASN1_SEQUENCE_ref(X509_REQ, 0, CRYPTO_LOCK_X509_INFO) = {
106*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ, req_info, X509_REQ_INFO),
107*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ, sig_alg, X509_ALGOR),
108*0Sstevel@tonic-gate ASN1_SIMPLE(X509_REQ, signature, ASN1_BIT_STRING)
109*0Sstevel@tonic-gate } ASN1_SEQUENCE_END_ref(X509_REQ, X509_REQ)
110*0Sstevel@tonic-gate
111*0Sstevel@tonic-gate IMPLEMENT_ASN1_FUNCTIONS(X509_REQ)
112*0Sstevel@tonic-gate IMPLEMENT_ASN1_DUP_FUNCTION(X509_REQ)
113