From 4c58cafc7e22ac109eef808fa9657485c37d24c6 Mon Sep 17 00:00:00 2001 From: Florian Eckert Date: Mon, 27 Jul 2026 15:47:59 +0200 Subject: [PATCH] strongswan: write local_key to swanctl.conf The 'local_key' UCI option was validated (checked for existence under /etc/swanctl/private/) but never written to the generated 'swanctl.conf'. As a result, setting 'local_key' had no actual effect on which private key was used for local authentication. Add the corresponding "privkeys" line to the local{} section, mirroring how local_cert is already written as "certs", so that swanctl explicitly uses the configured private key. Signed-off-by: Florian Eckert --- net/strongswan/files/swanctl.init | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/strongswan/files/swanctl.init b/net/strongswan/files/swanctl.init index 92916c9625..a7b1e11d84 100644 --- a/net/strongswan/files/swanctl.init +++ b/net/strongswan/files/swanctl.init @@ -553,6 +553,8 @@ config_remote() { [ -n "$local_identifier" ] && swanctl_xappend3 "id = \"$local_identifier\"" [ "$local_auth_method" = pubkey ] && [ -n "$local_cert" ] && \ swanctl_xappend3 "certs = $local_cert" + [ "$local_auth_method" = pubkey ] && [ -n "$local_key" ] && \ + swanctl_xappend3 "privkeys = $local_key" swanctl_xappend2 "}" swanctl_xappend2 "remote {"