Bug 893308

Summary:	certwatch doesn't support files with private keys
Product:	Red Hat Enterprise Linux 6	Reporter:	Jason Haar <jhaar>
Component:	crypto-utils	Assignee:	Joe Orton <jorton>
Status:	CLOSED ERRATA	QA Contact:	Stanislav Zidek <szidek>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.5	CC:	ebenes, jn, ksrot, salmy, szidek
Target Milestone:	rc	Keywords:	Regression, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	crypto-utils-2.4.1-24.3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-11 00:01:05 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:	1269913

Description Jason Haar 2013-01-09 05:42:31 UTC

Description of problem:

we don't separate our certs into .pem and .key files, instead we have ".cert" files containing both components. All OpenSSL products support that mode of operation, but certwatch doesn't

Version-Release number of selected component (if applicable):


How reproducible:

every time

Steps to Reproduce:
1. use certwatch on a file containing the private key and pubkey (in that order I guess)
2. certwatch exits with no error - even if the cert is about to expire
3.
  
Actual results:

no warning that your cert is about to expire.

Expected results:

a warning :-)

Additional info:

Comment 2 John Newbigin 2013-02-11 02:52:39 UTC

It seems that in EL4 (crypto-utils-2.1-4.3.el4) it could parse the key but now in EL6 it can not.

Comment 3 RHEL Program Management 2013-10-14 00:06:31 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Joe Orton 2014-02-13 22:52:45 UTC

Thanks for reporting this, it was a regression introduced with NSS support.  

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please
visit: https://www.redhat.com/support/process/production/#howto

Comment 23 errata-xmlrpc 2016-05-11 00:01:05 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-2016-0866.html