Add support for FIPS readiness check #99
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@saksarav-nokia to help tagging correct Nokia contact point. |
|
@wumiaont for viz |
judyjoseph
reviewed
Oct 8, 2025
This was referenced Oct 8, 2025
wumiaont
reviewed
Oct 8, 2025
Author
|
Requesting reviewers with write access to approve this PR, since all the review comments have been incorporated. |
|
@judyjoseph reminder on this. |
Author
|
reminder to approve the merge, if there are no comments/concerns. |
|
@judyjoseph : are we good to merge this ? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
No mechanism exists to query FIPS POST (Power-On Self-Test) status of the cryptographic backend module used by wpa_supplicant, preventing applications (like MACsec) from verifying FIPS compliance and cryptographic readiness.
How I did it
Command Line Interface
How to verify it
FIPS enabled enviornment
root@sonic:~$ /sbin/wpa_supplicant -F
FIPS POST status: pass (crypto backend: openssl)
non-FIPS enviornment
root@standard:~$ /sbin/wpa_supplicant -F
FIPS POST status: fail (crypto backend: openssl)