From: Jouni Malinen <j@w1.fi>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: consider Order bit to fill CCMP AAD
Date: Fri, 6 May 2022 11:02:44 +0300 [thread overview]
Message-ID: <20220506080244.GA866343@w1.fi> (raw)
In-Reply-To: <20220324004816.6202-1-pkshih@realtek.com>
On Thu, Mar 24, 2022 at 08:48:16AM +0800, Ping-Ke Shih wrote:
> Follow IEEE 802.11-21 that HTC subfield masked to 0 for all data frames
> containing a QoS Control field. It also defines the AAD length depends on
> QC and A4 fields, so change logic to determine length accordingly.
> diff --git a/net/mac80211/wpa.c b/net/mac80211/wpa.c
> @@ -317,13 +317,12 @@ static void ccmp_special_blocks(struct sk_buff *skb, u8 *pn, u8 *b_0, u8 *aad)
> /*
> * Mask FC: zero subtype b4 b5 b6 (if not mgmt)
> - * Retry, PwrMgt, MoreData; set Protected
> + * Retry, PwrMgt, MoreData, Order (if Qos Data); set Protected
> */
...
For completeness, we should really do the same got GCMP AAD which is
identical to the CCMP AAD. In other words, these changes should be done
in gcmp_special_blocks() as well. Those functions should really have
next to identical implementation for the AAD part (nonce construction is
different, though). There were already some differences in the design
before.. Maybe all this AAD stuff should really be moved into a separate
helper function that both CCMP and GCMP could use.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2022-05-06 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 0:48 [PATCH] mac80211: consider Order bit to fill CCMP AAD Ping-Ke Shih
2022-04-11 9:11 ` Johannes Berg
2022-04-12 0:37 ` Pkshih
2022-04-12 5:47 ` Johannes Berg
2022-04-13 0:24 ` Pkshih
2022-05-06 8:02 ` Jouni Malinen [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=20220506080244.GA866343@w1.fi \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).