-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NAS-131233 / 25.04 / Update to test for FIPS 3.0.9 #14629
Conversation
1d033c5
to
560f799
Compare
7e513ee
to
6bcd5aa
Compare
@sonicaj just pinging for review's sake |
@pytest.mark.skipif(not ha, reason='Test only valid for HA') | ||
def test_fips_version(): | ||
# The reason we have a set of commands in a payload is because of some annoying FIPS technicalities. | ||
# Basically, when FIPS is enabled, we can't use SSH because the SSH key used by root isn't using a FIPS provided algorithm. (this might need to be investigated further) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw you should be able to pull that off with -c aes128-ctr
iirc flag (not saying it's necessary but just sharing here)
This PR has been merged and conversations have been locked. |
This is the test for verifying our FIPS version, as well as checking that middleware reports the proper reboot reasons upon FIPS being enabled.
Enabling/disabling FIPS takes some time, so I also had to up the SSH command timeout through an optional argument.
This is paired with this PR to actually apply the new FIPS changes.
Passing tests as always