On Tue, 10 Mar 1998, William A. Arbaugh wrote:
> I'm using SSLeay in an embedded application. When I try and DER decode a
> DER encoded string into a X509 certificate with d2i_X509, the system size
> increases by ~60KB. Some of the symbols added are PKCS#7 functions, CRL
> functions etc. Does anyone know of a way to prevent those addtional
> functions from being linked in (without the obvious (and tedious) approach
> of adding a huge number of new #ifdefs)?
I remember seeing the PKCS#7 ones recently. I've written a perl script that,
given a function name, outputs the 'file' dependancy list. I'll try to
prune things down a bit.
eric
eg, d2i_X509.c pulls in the following files and I should be able to
avoid quite a few of them by choping things up a bit more...
a_bitstr.c a_bool.c a_bytes.c a_d2i_fp.c a_digest.c a_dup.c a_i2d_fp.c
a_int.c a_object.c a_octet.c a_print.c a_set.c a_sign.c a_type.c a_utctm.c
a_verify.c asn1_lib.c bio_lib.c bn_add.c bn_blind.c bn_div.c bn_exp.c bn_gcd.c
bn_lib.c bn_mod.c bn_mont.c bn_mul.c bn_mulw.c bn_rand.c bn_recp.c bn_shift.c
bn_sqr.c bn_sub.c bss_file.c buffer.c cryptlib.c d2i_dsap.c d2i_pu.c d2i_r_pr.c
d2i_r_pu.c d2i_s_pr.c d2i_s_pu.c dh_lib.c digest.c dsa_lib.c err.c ex_data.c
i2d_dsap.c i2d_pu.c i2d_r_pr.c i2d_r_pu.c i2d_s_pr.c i2d_s_pu.c lhash.c
md5_dgst.c md_rand.c mem.c names.c obj_dat.c obj_lib.c p7_dgst.c p7_enc.c
p7_enc_c.c p7_evp.c p7_i_s.c p7_lib.c p7_recip.c p7_s_e.c p7_signd.c p7_signi.c
p_lib.c p_sign.c p_verify.c rsa_eay.c rsa_lib.c rsa_none.c rsa_pk1.c
rsa_ssl.c stack.c x509_obj.c x_algor.c x_all.c x_attrib.c x_cinf.c x_crl.c
x_exten.c x_name.c x_pubkey.c x_req.c x_spki.c x_val.c x_x509.c
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
