Dr. Stephen Henson wrote:
Yes I tried lh_free. I call lh_free before I call EXTENSION_free. Using
valgrind I still
see a memory leak. It seems that in the r2i_pci call there is a
PROXY_CERT_INFO_EXTENSION_new
call. This memory is not being freed elsewhere. I don't see how the
LHASH memory is related
to the memory allocated in the PROXY_CERT_INFO_EXTENSION_new call. If
they are related let me know.
8 bytes in 1 blocks are definitely lost in loss record 1 of 3
==15976== at 0x1B9008D9: malloc (vg_replace_malloc.c:149)
==15976== by 0x1B93A280: default_malloc_ex (mem.c:79)
==15976== by 0x1B93A907: CRYPTO_malloc (mem.c:304)
==15976== by 0x1B9C9F68: asn1_item_ex_combine_new (tasn_new.c:191)
==15976== by 0x1B9CA280: ASN1_template_new (tasn_new.c:302)
==15976== by 0x1B9C9FF5: asn1_item_ex_combine_new (tasn_new.c:201)
==15976== by 0x1B9C9CA8: ASN1_item_ex_new (tasn_new.c:85)
==15976== by 0x1B9C9C74: ASN1_item_new (tasn_new.c:76)
==15976== by 0x1B9F089C: PROXY_CERT_INFO_EXTENSION_new (v3_pcia.c:55)
==15976== by 0x1B9F13EE: r2i_pci (v3_pci.c:283)
==15976== by 0x1B9E66F7: do_ext_nconf (v3_conf.c:159)
==15976== by 0x1B9E63FA: X509V3_EXT_nconf (v3_conf.c:90)
I have 2 questions.
1. Should I be able to call to create a proxyCertInfo extension by
making this call.
static char * pci_value = "critical, language:Inherit all";
ext = X509V3_EXT_conf(NULL, NULL, "proxyCertInfo", pci_value);
That is passing in NULL for the ctx and the LHASH object. I claim that
if I do this that causes
a segmentation fault. Has anybody else seen this behavior?
2. If I create a proxyCertInfo extension using the X509V3_EXT_conf call,
should I be able
to free the memory using only a X509_EXTENSION_free call? Since I did
not call
PROXY_CERT_INFO_EXTENSION_new, I don't think I should have to call
PROXY_CERT_INFO_EXTENSION_free.
Thanks,
Matt Rodriguez
On Mon, Dec 05, 2005, Matthew Rodriguez DSD staff wrote:
Dr. Stephen Henson wrote:
have you tried lh_free()? In fact you don't need an LHASH for this type of
extension in the way you use it so you should be able to pass it as NULL.
In
fact you can avoid X509V3_CTX as well and pass that as NULL.
I tried that first, but I also get a segmention fault when I pass the ctx in
as NULL.
Did you also try lh_free()?
Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Funding needed! Details on homepage.
Homepage: http://www.drh-consultancy.demon.co.uk
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
