RE: [PATCH 30/42] AP: MLD: Update all PMKSAs in the AP MLD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Tue, Nov 21, 2023 at 01:51:44AM +0200, Andrei Otcheretianski wrote:
> > When a non-AP MLD station associates with an AP MLD and the
> > association is a multi-link association, the PMKSA that is created as
> > part of the connection establishment is also relevant for the other
> > links included in the association.
> > Thus, update the PMKSA cache of the other BSSs (that are part of the
> > MLD connection) with the same PMKSA information.
> >
> > This is useful for cases, where after initial connection
> > establishment, the station disconnect and connects again, but instead
> > of using the original link for the connection it uses a different
> > link.
> 
> This does not feel correct. For AP MLD, it would make more sense to have a
> separate MLD level PMKSA cache for all non-AP MLDs. Or alternatively, such
> search the PMKSA cache entry from all affiliated APs instead of duplicating
> information into all BSSs.

I'm not completely sure what do you mean be MLD level PMKSA, but anyway, the second approach that you suggested to lookup the entry in all affiliated AP's is indeed better.
I'll resubmit a fixed version. Please drop this one.

> 
> --
> Jouni Malinen                                            PGP id EFC895FA

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux