Found an issue where users can end up with 0 byte PEM file on /etc/ssl/certs/cacert.pem
The way update_all is written - the mere existence of (bad 0 byte) file skips any cert fixes, so the user is stuck - getting "can't connect to internet" type errors. I can see a lot of people think it's their wifi etc.
My suggestions in no particular order -
1.
drop the /dev/null on so users can see if they are getting cert issues
curl ${CURL_SSL:-} --fail --location -o "${DOWNLOAD_PATH}" "${DOWNLOAD_URL}" &> /dev/null
2.
Modify the CASE statement:
60)
if [ -f /etc/ssl/certs/cacert.pem ] ; then
export CURL_SSL="--cacert /etc/ssl/certs/cacert.pem"
continue
fi
to also look for the existence of a 0 byte sized cacert.pem (& do something to fall through without the continue)
Found an issue where users can end up with 0 byte PEM file on /etc/ssl/certs/cacert.pem
The way update_all is written - the mere existence of (bad 0 byte) file skips any cert fixes, so the user is stuck - getting "can't connect to internet" type errors. I can see a lot of people think it's their wifi etc.
My suggestions in no particular order -
1. drop the /dev/null on so users can see if they are getting cert issues curl ${CURL_SSL:-} --fail --location -o "${DOWNLOAD_PATH}" "${DOWNLOAD_URL}" &> /dev/null
2. Modify the CASE statement:
60) if [ -f /etc/ssl/certs/cacert.pem ] ; then export CURL_SSL="--cacert /etc/ssl/certs/cacert.pem" continue fi
to also look for the existence of a 0 byte sized cacert.pem (& do something to fall through without the continue)