ASL 2.0 beta: Problems installing Zerotier, SSL and GPG related apparently

Howdy,

Understanding that “beat” is Latin for “It is broken” (OK, not really, but…) I’m noticing a couple things.

Background:

I’ve got a portable All Star node that I’m setting back up again. Because it’s nothing like mission critical, I installed the beta image onto it. I’ve got my tax.conf extensions.conf simplest tuning files and such all set up, and the node connects to things. Well, most things, but I think that’s on the other guy’s end.

However, when doing
Apt-get update
I get the following:

Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 http://apt.allstarlink.org/repos/asl_builds buster InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists… Done
W: Skipping acquire of configured file ‘rpi/source/Sources’ as repository ‘http://security.debian.org buster/updates InRelease’ doesn’t have the component ‘rpi’ (component misspelt in sources.list?)
W: Skipping acquire of configured file ‘rpi/binary-armhf/Packages’ as repository ‘http://security.debian.org buster/updates InRelease’ doesn’t have the component ‘rpi’ (component misspelt in sources.list?)
W: Skipping acquire of configured file ‘rpi/i18n/Translation-en’ as repository ‘http://security.debian.org buster/updates InRelease’ doesn’t have the component ‘rpi’ (component misspelt in sources.list?)

OK, does that just mean that Buster isn’t fully into current Saspbian?

Of slightly more concern is what happens when I try to install Zerotier, so I can take the portable node and easily get into it no matter what it’s connected to. Using the SSL script Zerotier provides (minus the silent switch):
curl https://install.zerotier.com | sudo bash

Nets me the following error:

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Google searches suggest some sort of certificate authority problem, but ca-certificates is up-to-date, and so are my system time and date.

It seems to me that this could lead to other problems. …

Any ideas on how to address what’s ailing default certificate stores?

Thanks,

Buddy Brannan, KB5ELV - Erie, PA
Email: buddy@brannan.name
Mobile: (814) 431-0962