Download
Browse source Changelog
Documentation
Project   Bug Bounty   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users Mailing lists Book: Everything curl Video presentations Report a bug Paid support
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: Curl and SSL in an IMB's OnDemand environment

From: Rainer Canavan via curl-library <curl-library_at_cool.haxx.se>
Date: Tue, 10 Sep 2019 17:34:53 +0200

On Tue, Sep 10, 2019 at 5:19 PM Michael Rellstab via curl-library
<curl-library_at_cool.haxx.se> wrote:
>
> Hi there!
>
> Since several days I'm trying out to get my project to work, but I don't have any success.
> Giving a short overview:
> I have to implement a UserExit (callback routine) for the IBM's OnDemand Software. Inside this UserExit I'm using CURL (linked as shared library).
> This works perfectly as long as I don't use an SSL secured communication. As soon as I activate SSL (TLS1.2), there is no communication anymore.
>
> I'm running on a CentOS with the NSS SSL framework compiled into CURL. When I use my UserExit without OnDemand (using the same source code, but executed by my main function),
> CURL runs together with NSS without any problems. As soon as my code runs in the context of OnDemand, SSL is not working anymore. I expect, this has to do with IBM's OnDemand, because they are using their GsKit as SSL framework.
>
> As you can see on my log output:
>
> 2019-09-10 15:11:07 DEBUG CURL version:7.29.0
[...]
> 2019-09-10 15:11:07 DEBUG CURL ssl version:NSS/3.34
[...]
> 2019-09-10 15:11:07 DEBUG == Info: Trying 192.168.27.108...
> 2019-09-10 15:11:07 DEBUG == Info: Connected to 192.168.27.108 (192.168.27.108) port 8443 (#0)
> 2019-09-10 15:11:07 DEBUG == Info: Curl_gskit_connect_nonblocking in

[...]

apparently the curl you're using is compiled with support for dynamic
ssl backends.
Try selecting NSS with https://curl.haxx.se/libcurl/c/curl_global_sslset.html

rainer
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-09-10