Re: [PATCH] mka: New MI should only be generated when peer's key is invalid

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

 



On Mon, Jan 07, 2019 at 07:18:23PM -0500, msiedzik@xxxxxxxxxxxxxxxxxxx wrote:
> From: Mike Siedzik <msiedzik@xxxxxxxxxxxxxxxxxxx>
> 
> Two recent changes to MKA create a situation where a new MI is generated
> every time a SAK Use parameter set is decoded.  The first change moved
> invalid key detection from ieee802_1x_decode_basic_body() to
> ieee802_1x_kay_decode_mpkdu():
> 
>   https://w1.fi/cgit/hostap/commit/?id=db9ca18bbff101da67c0cd7f482fe29ae694dc04
> 
> The second change forces the KaY to generate a new MI when an invalid
> key is detected:
> 
>   https://w1.fi/cgit/hostap/commit/?id=a8aeaf41df95ac6f979eb9014d0e2d17c46c671e
> 
> The fix is to move generation of a new MI from the old invalid key detection
> location to the new location.
> ---

Thanks! Could you please send this again with the Signed-off-by: line
added at the end of the commit message as described in the CONTRIBUTIONS
file so that I can apply this?

-- 
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