RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2029634 - sshd - should detect FIPS mode and handle tasks correctly in FIPS mode
Summary: sshd - should detect FIPS mode and handle tasks correctly in FIPS mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2021-12-13
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.0
Assignee: Rich Megginson
QA Contact: Jakub Haruda
Jan Fiala
URL:
Whiteboard: role:sshd
Depends On: 1942527
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-06 23:20 UTC by Rich Megginson
Modified: 2022-05-17 13:20 UTC (History)
9 users (show)

Fixed In Version: rhel-system-roles-1.11.0-1.el9
Doc Type: Bug Fix
Doc Text:
.The SSHD System Role can manage systems in FIPS mode Previously, the SSHD System Role could not create the `not allowed` HostKey type when called. As a consequence, the SSHD System Role could not manage RHEL 8 and older systems in Federal Information Processing Standard (FIPS) mode. With this update, the SSHD System Role detects FIPS mode and adjusts the default HostKey list correctly. As a result, the system role can manage RHEL systems in FIPS mode with the default HostKey configuration.
Clone Of: 1979714
Environment:
Last Closed: 2022-05-17 13:03:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github willshersystems ansible-sshd pull 173 0 None Merged Make the role FIPS-aware 2021-12-06 23:20:00 UTC
Red Hat Issue Tracker RHELPLAN-104915 0 None None None 2021-12-06 23:21:59 UTC
Red Hat Product Errata RHBA-2022:2443 0 None None None 2022-05-17 13:03:28 UTC

Description Rich Megginson 2021-12-06 23:20:00 UTC 
+++ This bug was initially created as a clone of Bug #1979714 +++

Description of problem:

The sshd role should handle managing a system which is in FIPS mode.  There may be tasks which should not be applied in FIPS mode, settings which are not applicable, etc.  Here is an example:

"We are attempting to use the SSH system role on RHEL7 systems which are in FIPS mode due to a security policy requirement. When trying to run this role through Ansible the playbook fails at SSH key generation task with error message "ED25519 keys are not allowed in FIPS mode". This is because the ed225519 key type is not available, as noted here: https://access.redhat.com/solutions/3643252."

There may be other tasks that will not work in FIPS mode, or other settings which should be skipped in FIPS mode.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
https://github.com/linux-system-roles/linux-system-roles.github.io/issues/66

--- Additional comment from Rich Megginson on 2021-07-06 22:41:53 UTC ---

@jjelen who should I assign this to?

--- Additional comment from Jakub Jelen on 2021-07-07 08:33:05 UTC ---

Its probably up to me. Thanks for heads up. I will check what we can do about that.

--- Additional comment from Jakub Jelen on 2021-07-07 08:44:13 UTC ---

FYI, the workaround posted in https://github.com/linux-system-roles/linux-system-roles.github.io/issues/66#issuecomment-875025844

  sshd_HostKey:
    - /etc/ssh/ssh_host_rsa_key
    - /etc/ssh/ssh_host_ecdsa_key

Is the correct solution for now and works for the reporter.

--- Additional comment from Jakub Jelen on 2021-11-09 19:59:38 UTC ---

Filled a PR adding this functionality in upstream:

https://github.com/willshersystems/ansible-sshd/pull/173

--- Additional comment from Rich Megginson on 2021-11-09 21:52:20 UTC ---

moving to ASSIGNED until merged upstream
Comment 3 Rich Megginson 2021-12-07 01:10:35 UTC 
@jjelen please provide the Doc Text
Comment 17 errata-xmlrpc 2022-05-17 13:03:10 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 (new packages: rhel-system-roles), 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-2022:2443
Note You need to log in before you can comment on or make changes to this bug.