From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 6/9] dpp-common: add TX/RX handlers to dpp_sm
Date: Mon, 15 Apr 2024 07:05:41 -0700 [thread overview]
Message-ID: <9f58f2a9-d2ba-4613-8613-9e44c1122e29@gmail.com> (raw)
In-Reply-To: <ae336a48-1606-47c4-a83e-59dc2560c1e6@gmail.com>
On 4/2/24 8:27 AM, Denis Kenzior wrote:
> Hi James,
>
> On 3/27/24 10:19, James Prestwood wrote:
>> This copies the bulk of the protocol handling from dpp.c into
>> dpp-common.c. There are no logical changes but some adaptations
>> needed to be made in order to isolate the encapsulating protocol
>> from the common protocol.
>>
>> - The DPP header is now reduced to not include the mmpdu header
>> or catagory byte.
>> - A channel switch must now notify the encapsulating protocol
>> since DPP common has no concept of frequency/channels
>> - When a peer is accepted its up to the encapsulating protocol
>> to filter frames only from this peer for the remainder of the
>> protocol. With PKEX the peer/own MACs actually do need to be
>> communicated to dpp-common due to some of the key generation.
>> - When a PKEX key is not set into the SM its up to the
>> encapsulating protocol to provide the key after a
>> PKEX_KEY_REQUESTED event. Once the key is obtained the SM
>> can resume the PKEX protocol.
>>
>
> There's a lot going on here, I think you're going to need to come up
> with a different strategy and break this patch up into digestible chunks.
>
Sure, I tried, but its just a nasty build breaking change :)
I can try and make some of the improvements ahead of time, add frame
handlers separately (auth/pkex/config/etc), then add the different events.
Thanks,
James
next prev parent reply other threads:[~2024-04-15 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 15:19 [PATCH 1/9] dpp: prep for moving AAD within dpp_append_wrapped_data James Prestwood
2024-03-27 15:19 ` [PATCH 2/9] dpp-util: move AAD logic within dpp_append_wrapped_attributes James Prestwood
2024-04-02 15:19 ` Denis Kenzior
2024-03-27 15:19 ` [PATCH 3/9] dpp-util: add dpp_append_point James Prestwood
2024-03-27 15:19 ` [PATCH 4/9] dpp: use dpp_append_point James Prestwood
2024-03-27 15:19 ` [PATCH 5/9] dpp-common: Skeleton for common DPP module James Prestwood
2024-03-27 15:19 ` [PATCH 6/9] dpp-common: add TX/RX handlers to dpp_sm James Prestwood
2024-04-02 15:27 ` Denis Kenzior
2024-04-15 14:05 ` James Prestwood [this message]
2024-03-27 15:19 ` [PATCH 7/9] build: add dpp-common.{c,h} James Prestwood
2024-03-27 15:19 ` [PATCH 8/9] dpp: remove most crypto/frame processing James Prestwood
2024-03-27 15:19 ` [PATCH 9/9] dpp: use common state machine James Prestwood
2024-04-02 15:10 ` [PATCH 1/9] dpp: prep for moving AAD within dpp_append_wrapped_data Denis Kenzior
2024-04-15 14:02 ` James Prestwood
2024-04-15 19:00 ` Denis Kenzior
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=9f58f2a9-d2ba-4613-8613-9e44c1122e29@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
/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