On Thu, 2025-05-15 at 14:36 +0200, Jan Hendrik Farr wrote: > On 13 19:45:45, Johannes Berg wrote: > > On Tue, 2025-05-13 at 19:36 +0200, Jan Hendrik Farr wrote: > > > > > So this test doesn't proof that it would work with the order the other way > > > around. Maybe I should try making iwd sleep while generating the commit. > > > > I guess you could, right. > > Just to report back on this: > > I added a 20ms delay in iwd's generation of the confirm message and > everything is working as expected with your patch applied. > Connection is succesful with the following order of frames > confirmed by external capture: > > 1. client sends SAE commit > 2. AP sends SAE commit > 3. AP sends SAE confirm > 4. client sends SAE confirm > Cool, good to know. I still think we shouldn't really do this unpaired (prepare/complete), but of course almost nothing except iwlwifi cares. But also iwlwifi shouldn't abort session protection for auth in this case anyway (or in the unlikely case of WEP shared key auth), unless the process is suspended/finished. johannes
