From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: linux-wireless@vger.kernel.org
Cc: miriam.rachel.korenblit@intel.com, johannes.berg@intel.com,
emmanuel.grumbach@intel.com, linux-kernel@vger.kernel.org,
Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Subject: [PATCH 0/2] wifi: iwlwifi: Fix WiFi operation in FIPS mode
Date: Mon, 29 Jun 2026 14:12:11 +0200 [thread overview]
Message-ID: <20260629121213.597038-1-jtornosm@redhat.com> (raw)
This series re-enables WiFi connectivity in FIPS mode for iwlwifi by
allowing Management Frame Protection (MFP/802.11w) to work with mac80211
software crypto.
Currently, iwlwifi connections fail in FIPS mode because commit
0636800c8ee1 (("wifi: iwlwifi: disable certain features for fips_enabled")
disabled MFP_CAPABLE when fips_enabled=1. The testing shows that MFP works
correctly in FIPS mode when mac80211 software crypto handles IGTK encryption
/decryption using FIPS-approved AES-CMAC/GMAC algorithms.
I think the original concern that "MFP since some frames need to be handled
in firmware" can be avoided for normal STA operation. The firmware-offload
requirement appears to apply specifically to features like WoWLAN and beacon
protection, which remain correctly disabled. AFAIK, for standard client
connections, management frames are processed only in software and mac80211
provides complete IGTK handling.
Patch 1 re-enables MFP_CAPABLE for iwlwifi to allow basic WiFi client
operation in FIPS mode. Patch 2 reduces a misleading warning message that
appears during normal FIPS operation to debug level - the warning actually
confirms that frames are not processed by firmware and are correctly handled
by software crypto instead.
Testing on Intel WiFi 6E AX210 with fips=1:
Before:
# cat /proc/sys/crypto/fips_enabled
1
# iw phy phy0 info | grep -A 10 "Cipher"
Supported Ciphers:
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
# nmcli connection up SSID
Error: Connection activation failed
After:
# cat /proc/sys/crypto/fips_enabled
1
# iw phy phy0 info | grep -A 10 "Cipher"
Supported Ciphers:
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
# nmcli connection up SSID
Connection successfully activated
# iw dev wlp7s0 station dump | grep MFP
MFP: yes
Jose Ignacio Tornos Martinez (2):
wifi: iwlwifi: enable MFP_CAPABLE in FIPS mode
wifi: iwlwifi: reduce encryption error message to debug level in FIPS mode
--
2.47.1
next reply other threads:[~2026-06-29 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:12 Jose Ignacio Tornos Martinez [this message]
2026-06-29 12:12 ` [PATCH 1/2] wifi: iwlwifi: enable MFP_CAPABLE in FIPS mode Jose Ignacio Tornos Martinez
2026-06-29 12:16 ` Johannes Berg
2026-06-29 12:45 ` Jose Ignacio Tornos Martinez
2026-06-29 13:02 ` Johannes Berg
2026-06-30 6:50 ` Jose Ignacio Tornos Martinez
2026-06-30 6:54 ` Johannes Berg
2026-06-30 7:20 ` Jose Ignacio Tornos Martinez
2026-06-30 7:25 ` Johannes Berg
2026-06-30 7:46 ` Jose Ignacio Tornos Martinez
2026-06-29 12:12 ` [PATCH 2/2] wifi: iwlwifi: reduce encryption error message to debug level " Jose Ignacio Tornos Martinez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260629121213.597038-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox