Bug 1713256

Summary: MD5 is used when writing password protected PEM
Product: Red Hat Enterprise Linux 8 Reporter: Jakub Jelen <jjelen>
Component: libsshAssignee: Anderson Sasaki <ansasaki>
Status: CLOSED ERRATA QA Contact: Ivan Nikolchev <inikolch>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: ansasaki, inikolch, omoris, qe-baseos-security, szidek, tmraz
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libssh-0.9.0-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1712436 Environment:
Last Closed: 2019-11-05 22:36:03 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: 1712436    
Bug Blocks:    

Comment 1 Jakub Jelen 2019-05-23 09:51:31 UTC
I added the following MR in gitlab, which is handling this problem:

https://gitlab.com/libssh/libssh-mirror/merge_requests/30

Though, it would be nice to take some more time with updating the testsuite hardcoded keys to be in the new format for testsuite to pass completely in FIPS mode.

Comment 2 Anderson Sasaki 2019-06-18 09:21:27 UTC
Encrypted keys in the new format were added to the test suite in:
https://gitlab.com/libssh/libssh-mirror/merge_requests/38

The test suite was adapted to run in FIPS mode in:
https://gitlab.com/libssh/libssh-mirror/merge_requests/40

Comment 8 errata-xmlrpc 2019-11-05 22:36:03 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://access.redhat.com/errata/RHBA-2019:3657