I don't have much information, but maybe someone has had a similar problem.
I am building my distribution of Apache Web Server (and Tomcat). I include in my tarball a compiled version of openssl, apr, apr-util and apache with several modules including mod_jk I build the components above in a physical machine running Solaris 10, create the tar ball and deploy it in another system (possibly in different directory, so we use LD_LIBRARY_PATH to point to the right set of libraries) All this has worked wonderful for quite some time. We have over the years updated several of the components with minor adjustment to our build. Currently we are using apache 2.2.20 with openssl 1.0.0d Recently our IT department decided to use Solaris zones; so they deployed the same tarball in a zone. It works fine for most of the users of the system, except for two of them. Their requests time out. The apache access and error logs don't show anything, but we were able to narrow it down to the SSL handshaking failing. So far, it seems that building openssl in the target machine (the solaris zone) fixes the problem; but I really want to distribute a compiled version of all libraries rather than building it in the target machine. So I was wondering if anybody has experienced a similar problem with OpenSSL when building it in a Soalris physical (global zone) machine but deploying it in a zone. -Jorge ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
