[Bug 1975576] Re: [SRU] Connect to WPA3 failed - Secrets were required, but not provided

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.104-0ubuntu2~20.04.2

---------------
netplan.io (0.104-0ubuntu2~20.04.2) focal; urgency=medium

  * Cherry pick d/p/dbus-Remove-the-upper-limit-on-try-timeout.patch
    (LP: #1967084)
  * Cherry-pick fix for rendering WPA3 password (8934a1b), LP: #1975576
    + d/p/0010-nm-fix-rendering-of-password-for-unknown-passthrough.patch
  * Backport offloading tristate patches (LP: #1956264)
    + d/p/0003-Add-tristate-type-for-offload-options-LP-1956264-270.patch
    + d/p/0004-tests-ethernets-fix-autopkgtest-with-alternating-def.patch
    + d/t/control: add 'ethtool' test-dep for link offloading tests

 -- Lukas Märdian <slyon at ubuntu.com>  Wed, 29 Jun 2022 17:54:23 +0200

** Changed in: netplan.io (Ubuntu Focal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1975576

Title:
  [SRU] Connect to WPA3 failed - Secrets were required, but not provided

Status in netplan.io package in Ubuntu:
  Fix Released
Status in netplan.io source package in Focal:
  Fix Released
Status in netplan.io source package in Impish:
  Won't Fix
Status in netplan.io source package in Jammy:
  Fix Released
Status in netplan.io source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
   * using network-manager (20/stable - 711 + netplan backend) and try to connect to router with WPA3 Security fails via "nmcli"
   * error message: "Error: Connection activation failed: (7) Secrets were required, but not provided."
   * related to a problem with the generation of the netplan configuration, when key management is "sae"
   * This breaks a customer setup in Ubuntu Core 20
   * The upstream fix solves the issue, by avoiding a shortcut in libnetplan's NetworkManager/keyfile renderer: https://github.com/canonical/netplan/pull/279

  [Test Plan]
   * Use a system with NetworkManager+netplan integration installed (e.g. Ubuntu Core, network-manager snap)
   * Create a WPA3 connection via "nmcli":
  $ sudo nmcli c add con-name test3 type wifi ssid ubuntu-wpa2-wpa3-mixed ifname wlan0
  Connection 'test3' (a89c5eb9-c5a4-426e-ae86-7fca5161cfcc) successfully added.
  $ sudo nmcli c modify test3 wifi-sec.key-mgmt sae wifi-sec.psk test1234

   * Make sure it contains the psk/credentials ("test1234") and "key-mgmt: sae":
  $ nmcli c show test3 --show-secrets | egrep "wireless-security.(key-mgmt|psk)"
  802-11-wireless-security.key-mgmt: sae
  802-11-wireless-security.psk: test1234
  802-11-wireless-security.psk-flags: 0 (none)

   * Make sure the netplan YAML contains "networkmanager.passthrough.key-mgmt: sae" and "auth.password: test1234":
  $ netplan get | grep password
  $ netplan get | grep key-mgmt

  [Where problems could occur]
   * The upload changes netplan's NetworkManager (keyfile) backend renderer. So any unexpected failure could break configuration of NetworkManager connection profiles via netplan.

  [Other Info]
   * upstream fix: https://github.com/canonical/netplan/pull/279
   * shipped as a hotfix in ppa:canonical-foundations/ubuntu-image: https://launchpad.net/~canonical-foundations/+archive/ubuntu/ubuntu-image/+sourcepub/13638052/+listing-archive-extra
   * related to private bug, LP: #1972800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1975576/+subscriptions