Swanctl error when PSK contains curly braces

[mamengoni]

Description

When configuring an IPsec connection, using a Pre-Shared Key (PSK) that contains curly braces {} causes swanctl to fail.

The issue is that the web interface does not report any validation error when saving the configuration. However, when the configuration is applied, swanctl returns an error and the connection does not start correctly.

Steps to reproduce

• Create a new IPsec connection
• Set a PSK containing a curly brace (e.g. test{123} )
• Save/apply the configuration
• Check swanctl --load-all

Expected behavior

• Properly handle PSKs containing curly braces, or
• Validate input in the UI and reject unsupported characters

Actual behavior

• No error shown in the UI
• Swanctl returns an error when loading the configuration

Components

NethSecurity - 8.7.2

[gsanchietti]

This is a proposed fix https://github.com/NethServer/nethsecurity/blob/c02eddd63321576a7accd5bbe6bc349b5ce82dd8/patches/feeds/packages/100-strongswan-swanctl-quote-psk.patch.
While it works, we fear some unexpcted regressions.
We are going to explore the possibility to create a validator

[gsanchietti]

Testing image: 8.7.2-dev+2b39dc060.20260514123813

Test case

• Try to edit a tunnel
• Add a curly bracket inside the pre-shared key field
• The UI should prevent the change

[mamengoni]

Tested and verified