Skip to main content

Hi, 

I have curl 8.4.0 with z/OS 2.4 and I am getting these errors:

OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to xxx.xxx.xxx.xxx:443

On the first request if failed with insufficient randomness, which points to /dev/random and /dev/random not working correctly, which led me to find out CSF was not started and the SAF resources was not defined. We got past that, the User ID using Curl has READ access to the following CSFSERV profiles :

CSNBRNG - Random Number Generate

CSFNRNGL - Random Number Generate Long

Now, is there any other profile that needs to be authorized for SSL to work ? I did peek the documentation and I could not find any references.

curl -V

curl 8.4.0 (i370-ibm-openedition) libcurl/8.4.0 OpenSSL/3.1.4
Release-Date: 2023-10-11
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy Largefile NTLM SSL TLS-SRP UnixSockets

Hi, 

I have curl 8.4.0 with z/OS 2.4 and I am getting these errors:

OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to xxx.xxx.xxx.xxx:443

On the first request if failed with insufficient randomness, which points to /dev/random and /dev/random not working correctly, which led me to find out CSF was not started and the SAF resources was not defined. We got past that, the User ID using Curl has READ access to the following CSFSERV profiles :

CSNBRNG - Random Number Generate

CSFNRNGL - Random Number Generate Long

Now, is there any other profile that needs to be authorized for SSL to work ? I did peek the documentation and I could not find any references.

curl -V

curl 8.4.0 (i370-ibm-openedition) libcurl/8.4.0 OpenSSL/3.1.4
Release-Date: 2023-10-11
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy Largefile NTLM SSL TLS-SRP UnixSockets

Hi Eduardo Rocha,

Could you please provide a little more detail about the environment and the error:


env | sort
curl -v https://google.com
curl -v your.server.here

Also, such errors may occur because of SSL processing on the proxy-server side...

Thanks,

Alexander

Terms & ConditionsAccessibility statement