On Tue, May 12, 2020 at 10:46:12PM +0100, Daniel Golle wrote:
> After hours of bisecting which change between hostapd_2_8 and
> hostapd_2_9 broke SAE in mesh mode with WolfSSL we got a result:
>
> > commit 6c9543fcb7962e26c2a91c43089abe171d073b44
> > Author: Jouni Malinen <jouni@xxxxxxxxxxxxxx>
> > Date: Thu Apr 25 20:18:27 2019 +0300
> >
> > Share common SAE and EAP-pwd functionality: random qr/qnr creation
> >
> > Use a shared helper function to create random qr/qnr values.
> >
> > Signed-off-by: Jouni Malinen <jouni@xxxxxxxxxxxxxx>
>
> While when building against OpenSSL, things keep working also after
> the above commit, when building against WolfSSL, the node hangs in
> LISTEN state for a long time and then ends up BLOCKED.
> I've tried with WolfSSL 3.14.4 and WolfSSL 4.3.0-stable-1 with
> identical results.
This works fine in my tests with 4.3.0. All the mac80211_hwsim test
cases for mesh pass with the current wpa_supplicant snapshot built with
WolfSSL 4.3.0.
> Going back to commit 2b84ca4dd
> ("Share common SAE and EAP-pwd functionality: suitable groups") makes
> things working again also with WolfSSL.
>
> On first sight there seems nothing wrong with that commit to me, but
> apparently it does break things :(
>
> Any ideas helping to fix this would be highly appreciated!
Can you please share some more details on how you are testing this and
ideally, debug logs from two devices for a case that fails with WolfSSL,
but works with OpenSSL? I'd like to also get a confirmation that you are
seeing the issue with the current snapshot of the master branch in
hostap.git since that is the version I would be using for any debugging
of the issue.
--
Jouni Malinen PGP id EFC895FA
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
