On 1/10/2013 11:28 AM, Amos Jeffries wrote:
On 10/01/2013 10:13 p.m., Eliezer Croitoru wrote:
On 1/7/2013 11:30 AM, Kinkie wrote:
Hi all,
   I've added a CentOS 6.3 node to the build farm, and set it up to
build trunk (not yet added to the main automated build run).
It shows brokenness in OpenSSL; may it be due to the API version fudge
by RedHat? Does anyone have any idea on how to fix already, or should
I embark in it?

Thanks,

--
     /kinkie

Where can I take a look at it?
When I had a problem I used a fedora openSSL RPM since the RH was broken.
If I can see the logs I can tell you if it's the same error.
I will look for the logs I had about it.

Eliezer

http://build.squid-cache.org/job/3.HEAD-amd64-centos-6/4/console

Amos

Thanks Amos,

This is indeed the same bug that was there for a long time in the 1.0.0 version of RH and friends.
Alex gave me before the link to this bug:
http://bugs.squid-cache.org/show_bug.cgi?id=3232

It was on FEDORA not CentOS but it seems like the same problem with OPENSSL_PSTRING.

In my build of CentOS I dropped for the 3.2.5 the dynamic cert so I dont know the exact status of CentOS.
They didn't had any updates\upgrades of OpenSSL for a very long time.

I am using:
##
Installed Packages
Name        : openssl
Arch        : x86_64
Version     : 1.0.0
Release     : 25.el6_3.1
Size        : 3.6 M
Repo        : installed
From repo   : updates
Summary     : A general purpose cryptography library with TLS implementation
URL         : http://www.openssl.org/
License     : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications between : machines. OpenSSL includes a certificate management tool and shared
            : libraries which provide various cryptographic algorithms and
            : protocols.
##

There were some patches before to make it work.
I dont know when RH or CentOS are planning to do something about it but Fedora branches are getting pretty fast upgrades for OpenSSL.

Build tests against a fixed version of OpenSSL for CentOS is good? or we want to stay compatible with the borken mainstream version?

Eliezer

Reply via email to