On Fri, Feb 21, 2020 at 04:01:47PM -0800, Duane Murphy wrote: > I’d like to validate my hostapd configuration by testing that I can login with a Windows 10 client. > > As a simple (?) test I thought I would use hostapd.eap_user. There are lots of nice entries pre-defined, but most of them don’t work with Windows 10. > > For example, Windows 10 no longer supports MD5 (out of the box). > > My knowledge of how to authenticate with Windows is fairly limited. Some help would be appreciated. > > I’ve tried several of the names and passwords in hostapd.eap_user but I have not been successful in authenticating. > > Do I need to configure Windows differently? Is there a different setting in hostapd.eap_user that I can use? It depends on what EAP method you want to use. If you just want to test something simple, PEAP with MSCHAPv2 has been available for a long time in various Windows versions. It could be configured with following style hostapd.eap_use entries: * PEAP "user" MSCHAPV2 "password" > Windows Authentication > > * Enable IEEE 8021.1x Authentication > * Microsoft: Protected EAP (PEAP) > * Authentication Method: Secured Password (EAP-MSCHAP v2) > * Enable Fast Reconnect — Selected > * Authentication Mode: User authentication Which would match those entries above. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
