That did it! The example uses X509_REQ_get_subject_name(CSR). X509_REQs now contain a pointer to a valid X509_NAME, so it's not necessary to allocate one. I was leaking the original one when I replaced it with the new one.
Thanks very much, Steve. Paul ___________________________________ Paul A. Suhler | Firmware Engineer | Quantum Corporation | Office: 949.856.7748 | paul.suh...@quantum.com ___________________________________ Disregard the Quantum Corporation confidentiality notice below. The information contained in this transmission is not confidential. Permission is hereby explicitly granted to disclose, copy, and further distribute to any individuals or organizations, without restriction. -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. Stephen Henson Sent: Saturday, May 30, 2009 4:56 PM To: openssl-users@openssl.org Subject: Re: Memory Leak Creating a CSR On Sat, May 30, 2009, Paul Suhler wrote: > Hi. > > Using OpenSSL 0.9.8i, I'm getting a memory leak when I create a CSR. > My process is taken more-or-less from the Viega, et al. book: > No idea what that version is but the one in demos/x509/mkreq.c doesn't leak memory. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. 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 majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
