SSH not working after enabling FIPS

kept internal to be used as needed.

Problem

A Member is required to enable FIPS(Federal Information Processing Standards) on their HI. After rebooting to finish enabling FIPS, the member was no longer able to SSH to their HI.

Solution

Me:

I did some digging and found an article that talks about SSH weirdness when FIPS mode is enabled. It explains why the SSH Key acts weird with FIPS and provides a workaround. Please let me know if it works for you and I will create documentation around this topic. - https://access.redhat.com/discussions/1518473#comment-938243

Device trying to SSH to FIPS enabled target must also have FIPS enable for SSH to be successfull.

Me:

I did some more digging as well, and I believe that you can use SSH with FIPS enabled as long as you are using FIPS-compliant keys/ciphers. However, there may be a Benchmark recommendation that is causing port 22 to become blocked.

I recommend you search through the relating benchmark for the recommendation that may be causing the issue - *insert link to build kit trouble article

I also found this documentation on enabling SSH with FIPS that you may find helpful.

https://docs.microsoft.com/en-us/cpp/linux/set-up-fips-compliant-secure-remote-linux-development?view=msvc-160

https://help.globalscape.com/help/eft7-4/mergedprojects/sftp/Enabling_FIPS_Mode_for_SSH_Connections.htm

Please let me know if you are able to get SSH working!

Keywords; FIPS

Content by Label

• Page:
  Feature Enhancement Requests for CIS Products