From 1ff4c95f115028cd3786f249ef77500767c904bf Mon Sep 17 00:00:00 2001
From: Ad Schellevis <ad@opnsense.org>
Date: Tue, 12 Nov 2024 18:15:11 +0100
Subject: [PATCH] firmware: when calling one of the predefined commands via our
 launcher, the environment should be initialized.

While debugging some missing TLS parameters, I noticed the ciphers where different than expected. Digging a bit deeper seemed to indicate env_init() wasn't called on my end.
If SELF should be the command, the intention was likely to pass the parameter instead of the script name (which is always launcher)

cc @fichtner
---
 src/opnsense/scripts/firmware/config.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/opnsense/scripts/firmware/config.sh b/src/opnsense/scripts/firmware/config.sh
index 7e15d19d5..54547f0c5 100755
--- a/src/opnsense/scripts/firmware/config.sh
+++ b/src/opnsense/scripts/firmware/config.sh
@@ -30,7 +30,7 @@ LOCKFILE=${LOCKFILE:-/tmp/pkg_upgrade.progress}
 BASEDIR="/usr/local/opnsense/scripts/firmware"
 PIPEFILE="/tmp/pkg_upgrade.pipe"
 FLOCK="/usr/local/bin/flock"
-SELF=$(basename ${0%.sh})
+SELF=$(basename ${1%.sh})
 TEE="/usr/bin/tee -a"
 PRODUCT="OPNsense"