problem calling new version; output of ... was "getssl.sh V2.46", expected "getssl V2.46"

[mpaolo]

Hi

weird, at some point cron run broke with msg:

problem calling new version; output of /tmp/tmp.67fngmEEyF -v was "getssl.sh V2.46", expected "getssl V2.46"

the cron script is simply

/root/.getssl/getssl.sh -u -a $@

it's run with no more args usually, guess that renaming getssl.sh as getssl fixes it, but it's been this way (getssl.sh) since 2018 working fine, so wonder if that's due to any recent change that makes it picky on shell script name too?

• OS: 4.9.0-17-amd64 #1 SMP Debian 4.9.290-1 (2021-12-12) x86_64 GNU/Linux
• GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

thx

[outoftheblue9]

I was getting the same error. I manually updated the version to 2.46. It seems the script running on the machine needs to be called getssl not getssl.sh for the auto update to work. Try renaming the file and see if it works.

[mpaolo]

...Try renaming the file and see if it works.

yes did the same in the meantime, I see the strict test on the string seems was introduced in pull 719.

not big deal provided it's documented, though may break auto-updates from eg cron (my case). I'd rather use a fingerprint check though, like:

in getssl:

MD5=
check=$(grep -v ^MD5= $0|md5sum |cut -d" " -f1)
[ "$MD5" != $check ] && echo Nok && exit 1 || echo ok

a release script would "pre-stamp" it duly:

MD5=$(grep -v ^MD5= getssl|md5sum |cut -d" " -f1)
sed -i s/^MD5=.*/MD5=$MD5/ getssl

thx