The booting mechanism is quiet different on systems like the raspberry pis. The correct time isn't yet set, so the ssl certificates of remote https servers will be invalid.
BusyBox v1.30.1 (Raspbian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ # /usr/bin/real_wget https://domain.tld
--1970-01-01 00:01:13-- https://domain.tld/
Resolving domain.tld (domain.tld)... 85.195.238.97
Connecting to domain.tld (domain.tld)|85.195.238.97|:443... connected.
ERROR: The certificate of 'domain.tld' is not trusted.
ERROR: The certificate of 'domain.tld' doesn't have a known issuer.
ERROR: The certificate of 'domain.tld' is not yet activated.
The certificate has not yet been activated
Simple workaround is to add an --no-check-certificate to the wget command in wget_or_ask. A more sophisticated workaround would be setting the correct time in initramfs.
The booting mechanism is quiet different on systems like the raspberry pis. The correct time isn't yet set, so the ssl certificates of remote https servers will be invalid.
Simple workaround is to add an
--no-check-certificateto the wget command inwget_or_ask. A more sophisticated workaround would be setting the correct time in initramfs.