cURL / Mailing Lists / curl-library / Single Mail

curl-library

Re: core dump after receiving a certificate

From: Kamil Dudka <kdudka_at_redhat.com>
Date: Thu, 29 Nov 2012 23:28:53 +0100

On Thursday, November 29, 2012 16:26:22 Rachel Quin wrote:
> ./a.out
> == Info: About to connect() to lb4.50.mia.megarouting.com port 443 (#0)
> == Info: Trying 10.50.0.41... == Info: connected
> == Info: Connected to lb4.50.mia.megarouting.com (10.50.0.41) port 443 (#0)
> == Info: Initializing NSS with certpath: sql:/etc/pki/nssdb
> == Info: skipping SSL peer certificate verification
> == Info: SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> == Info: Server certificate:
> == Info: subject:
> E=root_at_localhost.localdomain,CN=localhost.localdomain,OU=MyOrg,O=MyCompany,
> L=Seattle,ST=WA,C=-- == Info: start date: Mar 23 20:30:31 2012 GMT
> == Info: expire date: Mar 23 20:30:31 2013 GMT
> == Info: common name: localhost.localdomain
> == Info: issuer:
> E=root_at_localhost.localdomain,CN=localhost.localdomain,OU=MyOrg,O=MyCompany,
> L=Seattle,ST=WA,C=-- Segmentation fault (core dumped)
>
> Everything I try through libcurl dumps right after openssl gets the
> self-signed cert from the destination web server.
> I've set the locking functions for openssl, like in the example, but I
> still dump.

From the trace, it looks more likely that you are using NSS as the underlying
SSL library. So the locking functions for OpenSSL should not be necessary.

> How can I narrow down exactly why it's dumping on me?

Try to get a backtrace from the core with a debugger.

Please tell us also the version of libcurl and nss you are using.

Kamil
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-11-29