curl -k core dump

[Dan Ell]

We have been experiencing this on all the HPUX boxes. The command works fine without the -k oe --insecure option. It also works with the -k on our RedHat boxes. Anyone have any insight on this?

Linux Box...
$ curl -k https://mail.jbase.com

Object Moved

This document may be found
here

HPUX ...
$ curl -k https://mail.jbase.com
Memory fault(coredump)

[Steven Schweda]

> [...] all the HPUX boxes [...]

Not a very useful description.

uname -a

> curl [...]

Not a very useful description.

curl --version

Compare working with non-working systems.
(Particularly "Features:".)

Otherwise, apply a debugger to the "core"
file, and try to figure out what happened.

[Michael Steele_2]

Hi

Run again with -v / --verbose -or- --trace and get the error code. Must have error code!

curl --verbose
echo $?
-or-
curl --trace output_file
echo $?

Error codes:

http://curl.haxx.se/libcurl/c/libcurl-errors.html

[Steven Schweda]

> Memory fault(coredump)

> Must have error code!

If the program blows up in the middle, where
were you expecting to find this (whose?)
error (exit) code?

> echo $?

Not likely to be very informative.

[Michael Steele_2]

Steve, you're off your medication again.

Thorazine - to help treat extremely severe hyperexcitability in people who become easily combative and explosive without being provoked

[Steven Schweda]

Basic curiosity:

Does your cURL on your HP-UX system work any
better with an "http://" URL than it does
with an "https://" URL? For example:

curl -k http://mail.jbase.com

Where did you get this particular cURL kit?
(Pre-built, built it yourself, downloaded
from ...?)

Does it work at all with any URL?

On my convenient VMS system, I see:

alp $ curl --version
curl 7.19.3 (ALPHA-HP-VMS) libcurl/7.19.3 OpenSSL/0.9.8j
Protocols: tftp ftp telnet dict http file https ftps
Features: Largefile NTLM SSL

and it all works fine for me. My first guess
is that you're either missing that "SSL" in
the "Features:" list (and/or "https" in the
"Protocols:" list), or else there's something
else broken about your cURL program. But
with exactly no information about it, it's
hard to do more than guess.

[Dan Ell]

#uname -a
HP-UX usxxxx01 B.11.23 U 9000/800 655309333 unlimited-user license

#curl --version
curl 7.19.6 (hppa2.0w-hp-hpux11.23) libcurl/7.19.6 OpenSSL/0.9.8k zlib/1.2.3
Protocols: tftp ftp telnet dict http file https ftps
Features: IPv6 Largefile NTLM SSL libz

#curl --verbose -k https://mail.jbase.com
* About to connect() to mail.jbase.com port 443 (#0)
* Trying 198.145.183.67... connected
* Connected to mail.jbase.com (198.145.183.67) port 443 (#0)
* SSL: couldn't set callback!
* WARNING: failed to configure server name indication (SNI) TLS extension
Memory fault(coredump)


#curl --trace output_file -k https://mail.jbase.com
Segmentation fault (core dumped)

ouput_file is written as a zero-byte file

Works fine with http://mail.jbase.com

downloaded depot from hp for the curl "internet_A.13.00-013_HP-UX_B.11.23_IA_PA.depot"

[Steven Schweda]

I don't do much with cURL, even less on
HP-UX, and I tend to build such products from
the source rather than using a depot built by
someone else, so I know nothing, but my
uneducated guess is that your cURL program
was built using some relatively modern
version of OpenSSL ("0.9.8k"), but that you
don't actually have that OpenSSL installed on
your system, and the link-loader is finding
some older/incompatible OpenSSL fossil, and
trying to run with that (with limited
success).

Looking at the cURL 7.19.7 source (which I
have at hand), the message "SSL: couldn't set
callback!" seems to be coming from some code
bounded by
#ifdef SSL_CTRL_SET_MSG_CALLBACK
and a nearby comment says:

/* The SSL_CTRL_SET_MSG_CALLBACK doesn't exist in ancient OpenSSL versions
and thus this cannot be done there. */

This suggests the possibility that your cURL
program is calling OpenSSL stuff which
doesn't really exist on your system.

So, I'd either try building cURL from the
source, or else installing an OpenSSL depot
which might be consistent with what was used
to build that cURL depot.


Note that one man's "ancient" may not be very
well defined, so I'd look for an OpenSSL at
least as new as 0.9.8k. (0.9.8l seems to be
the current one.)