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):
Steps to Reproduce:
@jjelen who should I assign this to?
Its probably up to me. Thanks for heads up. I will check what we can do about that.
FYI, the workaround posted in https://github.com/linux-system-roles/linux-system-roles.github.io/issues/66#issuecomment-875025844
Is the correct solution for now and works for the reporter.
Filled a PR adding this functionality in upstream:
moving to ASSIGNED until merged upstream
@jjelen please provide Doc Text
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 (rhel-system-roles 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.