Bug 1335097

Summary: openssl contains time bomb
Product: Red Hat Enterprise Linux 6 Reporter: Tuomo Soini <tis>
Component: opensslAssignee: Tomas Mraz <tmraz>
Status: CLOSED ERRATA QA Contact: Stanislav Zidek <szidek>
Severity: high Docs Contact:
Priority: high    
Version: 6.8CC: ajb, cww, gnaik, hongjiu.lu, jfenal, johnny, nmavrogi, rajeshrj_is, redhat-bugzilla, riehecky, szidek, toracat
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openssl-1.0.1e-48.el6_8.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 10:11:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269194, 1343211    
Attachments:
Description Flags
This patch updates the expired certificates. none

Description Tuomo Soini 2016-05-11 11:05:54 UTC
openssl-1.0.1e-48.el6 and openssl-1.0.1e-48.el6_8.1 both contains time bomb and they can't be rebuild any more because certificates in tests have been expired at 2016-05-10.

perl cms-test.pl
CMS => PKCS#7 compatibility tests
signed content DER format, RSA key: verify error
make: Leaving directory `/builddir/build/BUILD/openssl-1.0.1e/test'
make: *** [test_cms] Error 1

I suggest quick fix so you can continue providing security fixes for openssl.

Reference:

https://groups.google.com/forum/#!topic/mailing.openssl.dev/d1q9rY6KFtk

Comment 2 Robert Scheck 2016-05-11 22:12:53 UTC
I run into the same issue while backporting the openssl-1.0.1e-48.el6_8.1
changes to openssl101e for EPEL 5. The following upstream patch solves the
issue for me and applied without manual merging:

http://pkgs.fedoraproject.org/cgit/rpms/openssl101e.git/tree/openssl-1.0.1e-update-test-certs.patch?h=el5

Comment 3 Fedora Update System 2016-05-11 23:46:03 UTC
openssl101e-1.0.1e-8.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-92e8b90065

Comment 4 Fedora Update System 2016-05-12 21:18:32 UTC
openssl101e-1.0.1e-8.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-92e8b90065

Comment 5 Robert Scheck 2016-05-12 21:21:46 UTC
Sorry, I didn't want to hijack this RHBZ, removed the RHBZ from my update.

Could somebody please reset the state to NEW? Because this one is for the
OpenSSL as shipped by RHEL - thanks!

Comment 6 Rajesh RJ 2016-05-18 16:58:49 UTC
we hit the  smime-certs  expired issue with our rpm build process . We were using 
openssl-1.0.0-20.el6_2.5.src.rpm for our rpm builds.

Do we know when an rpm patch will be available with the updated certs ?

Thanks.

Comment 7 Tomas Mraz 2016-05-18 22:30:15 UTC
Rajesh, do you mean updated package for RHEL-6.2 EUS? Please request any such updates via the support channels.

Comment 8 Rajesh RJ 2016-05-19 02:32:39 UTC
Thomas,

I' am looking for the updated source rpm for CentOS as our rpm build gets source RPM from centos.org. I raised this issue with centos.org when I noticed this issue (https://bugs.centos.org/view.php?id=10843).

Comment 9 manuel wolfshant 2016-05-19 08:37:07 UTC
openssl-1.0.0-20.el6_2.5.src.rpm  looks like an EUS package and those are NOT available for people without a proper RHEL subscription.

Comment 13 Tomas Mraz 2016-07-12 09:19:52 UTC
Created attachment 1178815 [details]
This patch updates the expired certificates.

Comment 22 errata-xmlrpc 2017-03-21 10:11:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0660.html