Bug 1744108

Summary:	ssh-keyscan doesn't recognize rsa keys in fips mode
Product:	Red Hat Enterprise Linux 8	Reporter:	Ivan Nikolchev <inikolch>
Component:	openssh	Assignee:	Jakub Jelen <jjelen>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Moriš <omoris>
Severity:	low	Docs Contact:	Jan Fiala <jafiala>
Priority:	low
Version:	8.0	CC:	jafiala, jjelen, omoris, pasik, tmraz
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	jjelen: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openssh-8.0p1-5.el8	Doc Type:	Bug Fix
Doc Text:	.`ssh-keyscan` recognizes RSA keys in FIPS mode The `SHA-1` algorithm is disabled for RSA signatures in FIPS mode, which previously prevented the `ssh-keyscan` utility from retrieving RSA keys of servers operating in that mode. With this update, `ssh-keyscan` recognizes RSA keys in FIPS mode and therefore can retrieve these keys from servers in FIPS mode correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:31:59 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:

Description Ivan Nikolchev 2019-08-21 11:20:07 UTC

Description of problem:
ssh-keyscan doesn't recognize rsa keys in fips mode

Version-Release number of selected component (if applicable):
openssh-8.0p1-3.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1.ssh-keygen -t rsa -N '' -f ~/.ssh/id_rsa
2.ssh-keyscan -t rsa localhost
3.

Actual results:
No key shown

Expected results:
Key is printed

Additional info:
Upstream bug is linked and already fixed.

Comment 15 errata-xmlrpc 2020-11-04 01:31:59 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 (openssh bug fix and enhancement update), 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-2020:4439