Why are you running on such an old OS? How old are your Windows and Linux systems? Certainly not of the same generation.
Solaris 8 & 9 are no longer supported, so you can't get security patches or anything. I highly recommend you try at least S10, or better, yet - S11. the /dev/[u]random on S8 is a far cry from what is in our modern OSes. Valerie On 11/13/2015 12:38 PM, Tom Kacvinsky wrote:
---------- Forwarded message ---------- From: *Tom Kacvinsky* <[email protected] <mailto:[email protected]>> Date: Tue, Nov 10, 2015 at 5:51 PM Subject: Solaris 8, OpenSSL 1.0.1e, not connecting fro our client, but can connect via openssl in client mode To: [email protected] <mailto:[email protected]> I have an interesting case where I am using Solaris 8 (the patchset for which which has /dev/urandom and /dev/random) with OpenSSL 1.0.1e. I can see from my truss logs that we are attempting to connect to a secure web server, but we see nothing in the Apache log files indicating we connect. If I run ./openssl s_client -ssl3 -host XXX.vectorcast.com <http://XXX.YYY.com> -port 443 we do indeed connect. So I suspect it is something in the client code we are using. We are using the Qt 4.8.5 SSL client. What should I be on the look out for, so I can file a reasonable support request with Digia? This code works fine on Linux and Windows, so I don't really know at this point if the problem is with Solaris support in Qt, or something lower level in OpenSSL (thought I doubt the latter as openssl in client mode is able to connect). Thanks, Tom _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
-- Valerie Fenwick, http://bubbva.blogspot.com/ @bubbva Solaris Cryptographic & Key Management Technologies, Manager Oracle Corporation: 4180 Network Circle, Santa Clara, CA, 95054. _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
