From: Johannes Berg <johannes@sipsolutions.net>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
linux-wireless@vger.kernel.org
Cc: miriam.rachel.korenblit@intel.com, emmanuel.grumbach@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] wifi: iwlwifi: enable MFP_CAPABLE in FIPS mode
Date: Mon, 29 Jun 2026 14:16:34 +0200 [thread overview]
Message-ID: <297578c2a1293523a28896f30031db16ccd26bd0.camel@sipsolutions.net> (raw)
In-Reply-To: <20260629121213.597038-2-jtornosm@redhat.com>
On Mon, 2026-06-29 at 14:12 +0200, Jose Ignacio Tornos Martinez wrote:
> Re-enable MFP_CAPABLE flag in FIPS mode for iwlwifi to allow Management
> Frame Protection (802.11w) to work with mac80211 software crypto.
>
> Commit 0636800c8ee1 ("wifi: iwlwifi: disable certain features for
> fips_enabled") disabled MFP_CAPABLE when fips_enabled=1.
> I think the original concern about "some frames need to be handled in
> firmware" applies to firmware-offloaded features like WoWLAN and beacon
> protection, which remain correctly disabled by the commented commit.
No, you think wrong, this cannot be done.
johannes
next prev parent reply other threads:[~2026-06-29 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:12 [PATCH 0/2] wifi: iwlwifi: Fix WiFi operation in FIPS mode Jose Ignacio Tornos Martinez
2026-06-29 12:12 ` [PATCH 1/2] wifi: iwlwifi: enable MFP_CAPABLE " Jose Ignacio Tornos Martinez
2026-06-29 12:16 ` Johannes Berg [this message]
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=297578c2a1293523a28896f30031db16ccd26bd0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=jtornosm@redhat.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