All geek questions in one place

Why is Perl Crypt :: SSLeay timeout on Intel Mac OS X computers?

A has a Perl cron job, which recently started with the launch of its HTTPS connections with the error "500 SSL read timeouts." I noticed that the error is being triggered as part of the alarm in Crypt :: SSLeay , but I don’t know if this is just something too long to respond.

So far, I have configured a timeout from 30 seconds to 10 minutes, and it still does not work. I moved the script to other computers, and those that were on Intel Mac OS X systems time out, while those on Linux or Mac OS X PPC systems work fine, so I don’t think that it has changed in the network or the remote server.

When the process started with problems, it does not coincide with software updates or reboots on the computer, and I contacted the server to which I connect, and everyone claims that they did not change anything.

Does anyone have any recommendations on trying to debug HTTPS, or have you ever seen this behavior and made recommendations on something that I might overlook that might cause this problem?

+4
source share
1 answer

The problem seems to be specific to OS X and is directly related to OpenSSL, so it is not unique to perl. Perhaps this is due to one of the latest security updates from Apple (2010-001).

I have the same problem:

  • python httplib (uploads over ~ 64k, throws an error "Read operation error"). Smaller loading through work with SSL. HTTP downloads of all sizes work.

  • HTTPS twisting. curl times. The same curl command from Linux works great with both HTTP and HTTPS. curl on OS X over HTTP also works great.

I found several places on the Internet that cover similar problems in different programming languages ​​/ software. I can publish only one ... https://blog.torproject.org/blog/apple-broke-openssl-which-breaks-tor-os-x

+3
source

Source: https://habr.com/ru/post/1301159/

More articles:


All Articles