Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ainy.kumari@oss.qualcomm.com,
	sai.magam@oss.qualcomm.com, quic_drohan@quicinc.com
Subject: Re: [PATCH wireless-next v4 0/9] wifi: cfg80211/mac80211: Add Support for EPPKE Authentication
Date: Mon, 19 Jan 2026 12:36:10 +0530	[thread overview]
Message-ID: <df708bef-7300-4df1-a5b1-9acd2c346fe9@oss.qualcomm.com> (raw)
In-Reply-To: <4f8e174edf63c00f3c277e86e7de472fb7520422.camel@sipsolutions.net>


On 1/16/2026 1:47 PM, Johannes Berg wrote:
> On Wed, 2026-01-14 at 16:48 +0530, Kavita Kavita wrote:
>> This patch series introduces support for the Enhanced Privacy
>> Protection Key Exchange (EPPKE) authentication protocol, as defined in
>> "IEEE P802.11bi/D3.0, 12.16.9". The implementation covers both AP and
>> non-AP STA modes, with clear separation in the commit descriptions.
>>
>> The changes have been validated end-to-end using the hwsim tool.
>>
>> During development and testing of EPPKE feature, we encountered an
>> issue in mac80211 related to incorrect AAD/Nonce computation for
>> management frames when MLO address translation is involved.
>> Depends-on: [PATCH wireless-next] wifi: mac80211: Fix AAD/Nonce
>> computation for management frames with MLO
>>
>> Without the patch, EPPKE functionality will fail for MLO connection.
> Because of that, I've only applied patches 1-8 for now, so the feature
> isn't enabled anywhere until we fix that issue.


Sure, Thank you.


>
> johannes

      reply	other threads:[~2026-01-19  7:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 11:18 [PATCH wireless-next v4 0/9] wifi: cfg80211/mac80211: Add Support for EPPKE Authentication Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 1/9] wifi: cfg80211: add support for EPPKE Authentication Protocol Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 2/9] wifi: cfg80211: add feature flag for (re)association frame encryption Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 3/9] wifi: cfg80211: add support for key configuration before association Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 4/9] wifi: nl80211: Add support for EPP peer indication Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 5/9] wifi: mac80211: allow key installation before association Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 6/9] wifi: mac80211: Check for MLE before appending in Authentication frame Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 7/9] wifi: mac80211: add support for EPPKE authentication protocol in non-AP STA mode Kavita Kavita
2026-01-14 11:18 ` [PATCH wireless-next v4 8/9] wifi: mac80211: add support for encryption/decryption of (Re)Association frames Kavita Kavita
2026-01-14 11:19 ` [PATCH wireless-next v4 9/9] wifi: mac80211_hwsim: Declare support for EPPKE authentication protocol Kavita Kavita
2026-01-16  8:17 ` [PATCH wireless-next v4 0/9] wifi: cfg80211/mac80211: Add Support for EPPKE Authentication Johannes Berg
2026-01-19  7:06   ` Kavita Kavita [this message]

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=df708bef-7300-4df1-a5b1-9acd2c346fe9@oss.qualcomm.com \
    --to=kavita.kavita@oss.qualcomm.com \
    --cc=ainy.kumari@oss.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_drohan@quicinc.com \
    --cc=sai.magam@oss.qualcomm.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