Bug 1812844

Summary:	FIPS: add "ssh-rsa" to PubkeyAcceptedKeyTypes for openssh-server
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	crypto-policies	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	jjelen, nmavrogi
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 11:14:41 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 Renaud Métrich 2020-03-12 10:36:06 UTC

Description of problem:

Customers connecting to a FIPS system using PuTTY client cannot connect because "ssh-rsa" is not part of the PubkeyAcceptedKeyTypes option line passed to sshd in /etc/crypto-policies/back-ends/opensshserver.config.


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

crypto-policies-20190807-1.git9b1477b.el8.noarch


How reproducible:

Always


Steps to Reproduce:
1. Enable FIPS on a RHEL 8 system
2. Try connecting with PuTTY using a generated key from PuTTY client (defaults to "ssh-rsa")

Actual results:

userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedKeyTypes [preauth]


Expected results:

No issue connecting

Comment 1 Tomas Mraz 2020-03-12 11:14:41 UTC

That would enable SHA1 signatures and we do not want to do that.
They should be able to use ECDSA keys with PuTTY if RSA-SHA256 signatures are not supported by it.

Jakub, can you please confirm what I am saying above?