https://bugs.kde.org/show_bug.cgi?id=457249

Baldrun Orv <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #2 from Baldrun Orv <[email protected]> ---
I can confirm this issue on current versions and would like to add some
technical details that may help with implementing it.

ENVIRONMENT:
Operating System: Manjaro Linux 
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 6.18.39-1-MANJARO (64-bit)
Graphics Platform: Wayland
plasma-nm: 6.7.3-1
strongswan: 6.0.7-1
networkmanager-strongswan: 1.6.4-1
networkmanager 1.56.1-2

SYMPTOM: 
In the connection editor for "IPsec/IKEv2 (strongswan)" connections, the
"Authentication" dropdown only offers: Certificate/private key,
Certificate/ssh-agent, Smartcard, and EAP. There is no PSK option, although the
underlying strongSwan NetworkManager backend (charon-nm) has supported
method=psk for years — see src/charon-nm/nm/nm_service.c in the strongSwan
sources, and the GNOME editor (network-manager-strongswan) exposes it.

REAL-WORLD-IMPACT: 
IKEv2 road-warrior setups with PSK authentication are common on commercial
gateways (in my case a LANCOM firewall used in a small law office). With the
current dialog, such connections cannot be configured in Plasma at all.

WORKAROUND: 
(for anyone else hitting this): create the connection in the GUI, then set the
method outside the dialog:
 > nmcli connection modify "<name>" +vpn.data "method=psk"
 > nmcli connection modify "<name>" +vpn.data "user=<IKE identity>"
The secret is stored under the key password (KWallet or [vpn-secrets] in the
keyfile). This works and I have such a connection running.

One additional pitfall for the implementation: 
since the dialog does not know method=psk, re-saving a connection in the GUI
silently resets the method to one of the four known values, breaking a
previously working (nmcli-configured) PSK connection. So even before full UI
support, it would help if unknown method values were preserved on save.

Note for the UI design: 
charon-nm enforces a minimum PSK length of 20 characters ("Pre-shared key is
too short."), so the input field should ideally validate/hint this.

Happy to test patches.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to