public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Peddolla Harshavardhan Reddy <peddolla.reddy@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, kavita.kavita@oss.qualcomm.com
Subject: Re: [PATCH wireless-next v2 15/16] wifi: cfg80211: add LTF keyseed support for secure ranging
Date: Wed, 04 Mar 2026 13:03:01 +0100	[thread overview]
Message-ID: <8669fc9bcc8250ec71ddb293da5022881ba714a8.camel@sipsolutions.net> (raw)
In-Reply-To: <20260304071538.3833062-16-peddolla.reddy@oss.qualcomm.com>

On Wed, 2026-03-04 at 12:45 +0530, Peddolla Harshavardhan Reddy wrote:
> 
>   * @NL80211_CMD_NEW_KEY: add a key with given %NL80211_ATTR_KEY_DATA,
>   *	%NL80211_ATTR_KEY_IDX, %NL80211_ATTR_MAC, %NL80211_ATTR_KEY_CIPHER,
> - *	and %NL80211_ATTR_KEY_SEQ attributes. %NL80211_ATTR_MAC represents
> - *	peer's MLD address for MLO pairwise key. The link to add MLO
> - *	group key is identified by %NL80211_ATTR_MLO_LINK_ID.
> + *	%NL80211_ATTR_KEY_SEQ and %NL80211_KEY_LTF_SEED attributes.
> + *	%NL80211_ATTR_MAC represents peer's MLD address for MLO pairwise key.
> + *	The link to add MLO group key is identified by
> + *	%NL80211_ATTR_MLO_LINK_ID.

I think this is a bit misleading since it mixes up the key attributes
now. I think at this level it should refer to %NL80211_ATTR_KEY instead
of the specific nested %NL80211_KEY_LTF_SEED.

>   * @NL80211_CMD_DEL_KEY: delete a key identified by %NL80211_ATTR_KEY_IDX
>   *	or %NL80211_ATTR_MAC. %NL80211_ATTR_MAC represents peer's MLD address
>   *	for MLO pairwise key. The link to delete group key is identified by
> @@ -5602,6 +5603,14 @@ enum nl80211_key_default_types {
>   * @NL80211_KEY_MODE: the mode from enum nl80211_key_mode.
>   *	Defaults to @NL80211_KEY_RX_TX.
>   * @NL80211_KEY_DEFAULT_BEACON: flag indicating default Beacon frame key
> + * @NL80211_KEY_LTF_SEED: LTF key seed is used by the driver to generate
> + *	secure LTF keys used in case of peer measurement request with FTM
> + *	request type as either %NL80211_PMSR_FTM_REQ_ATTR_NON_TRIGGER_BASED
> + *	or %NL80211_PMSR_FTM_REQ_ATTR_TRIGGER_BASED, secure LTF key seeds will
> + *	help enable PHY security in peer measurement session. The corresponding
> + *	keys need to be configured before hand to ensure peer measurement

"beforehand"

> + *	session is secure. Only valid if %NL80211_EXT_FEATURE_SECURE_LTF
> + *	is set.

NL80211_EXT_FEATURE_SECURE_LTF already exists today, and is set by
iwlwifi/mvm, so I'm not convinced you can just redefine it to mean also
LTF key seed is supported?

> +++ b/net/wireless/nl80211.c
> @@ -983,6 +983,7 @@ static const struct nla_policy nl80211_key_policy[NL80211_KEY_MAX + 1] = {
>  	[NL80211_KEY_TYPE] = NLA_POLICY_MAX(NLA_U32, NUM_NL80211_KEYTYPES - 1),
>  	[NL80211_KEY_DEFAULT_TYPES] = { .type = NLA_NESTED },
>  	[NL80211_KEY_MODE] = NLA_POLICY_RANGE(NLA_U8, 0, NL80211_KEY_SET_TX),
> +	[NL80211_KEY_LTF_SEED] = { .type = NLA_BINARY, .len = 48 },

This probably doesn't do what you think it does, unless you really
wanted that it's *at most* 48 bytes. And please add a define in
ieee80211.h for that.

johannes

  reply	other threads:[~2026-03-04 12:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  7:15 [PATCH wireless-next v2 00/16] wifi: Ranging support enhancements Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 01/16] wifi: cfg80211: Allow RSTA role without LMR request Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 02/16] wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 03/16] wifi: cfg80211: Add MAC address filter to remain_on_channel Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 04/16] wifi: cfg80211/mac80211: Add NL80211_IFTYPE_PD for PD PASN and PMSR operations Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 05/16] wifi: cfg80211: add start/stop proximity detection commands Peddolla Harshavardhan Reddy
2026-03-04 11:47   ` Johannes Berg
2026-03-05 15:33     ` Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 06/16] wifi: cfg80211: add proximity detection capabilities to PMSR Peddolla Harshavardhan Reddy
2026-03-04 11:50   ` Johannes Berg
2026-03-05 15:34     ` Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 07/16] wifi: cfg80211: add continuous ranging and PD request support Peddolla Harshavardhan Reddy
2026-03-04 11:52   ` Johannes Berg
2026-03-05 15:38     ` Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 08/16] wifi: cfg80211: extend PMSR FTM response for proximity ranging Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 09/16] wifi: cfg80211: add role-based PD peer limits Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 10/16] wifi: cfg80211: add ingress/egress distance thresholds for FTM Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 11/16] wifi: cfg80211: add PD-specific preamble and bandwidth capabilities Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 12/16] wifi: cfg80211: add FTM range report negotiation support Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 13/16] wifi: cfg80211: add result reporting control for PD requests Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 14/16] wifi: cfg80211: add MAC randomization support " Peddolla Harshavardhan Reddy
2026-03-04 11:56   ` Johannes Berg
2026-03-05 15:42     ` Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 15/16] wifi: cfg80211: add LTF keyseed support for secure ranging Peddolla Harshavardhan Reddy
2026-03-04 12:03   ` Johannes Berg [this message]
2026-03-05 15:48     ` Peddolla Harshavardhan Reddy
2026-03-04  7:15 ` [PATCH wireless-next v2 16/16] wifi: mac80211_hwsim: Add support for extended FTM ranging Peddolla Harshavardhan Reddy

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=8669fc9bcc8250ec71ddb293da5022881ba714a8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kavita.kavita@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peddolla.reddy@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