PMF is controlled from AP side over which - mine is always PMF required with 
SAE, for instance, even if it's optional for WPA-PSK on the same SSID.
(that's a configurable option)

PMF should be enabled if at all possible.  PMF optional : mode 1 - recommended 
as long as the driver supports it, and pmf 2 - required - should be the other 
choice.   PMF disabled is only for systems where security is not an issue or 
the driver is known not to function.
It should raise a security alert if PMF is disabled. (eg: warning: this reduces 
security considerably)

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.

  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
Status in network-manager package in Ubuntu:

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to