ikarso has quit [Quit: Connection closed for inactivity]
sts-q has quit [Ping timeout: 260 seconds]
sts-q has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
set_ has quit [Remote host closed the connection]
ikarso has joined #beagle
vd626 has joined #beagle
vd62 has quit [Ping timeout: 256 seconds]
vd62657 has joined #beagle
vd626 has quit [Ping timeout: 256 seconds]
vd62657 has quit [Quit: Client closed]
vd62657 has joined #beagle
Raajeshwar has joined #beagle
<Raajeshwar>
Hi, I was working with Beaglebone AI. I could not configure pins using config-pin command. pinmux file not found! and Pin has no cape: errors are thrown. Should I change something in uEnv.txt?
vd626576 has joined #beagle
vd62657 has quit [Ping timeout: 256 seconds]
vd626576 has quit [Quit: Client closed]
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
ketas- has joined #beagle
bldr_ has joined #beagle
bldr has quit [Ping timeout: 260 seconds]
ketas has quit [Ping timeout: 260 seconds]
Raajeshwar has quit [Ping timeout: 256 seconds]
florian has joined #beagle
Raajeshwar has joined #beagle
<zmatt>
kveremitz: isn't the whole point of matrix that it's a decentralized system, so it doesn't matter what homeserver you use?
Raaj has joined #beagle
Raaj has left #beagle [#beagle]
Raaj has joined #beagle
Raaj has left #beagle [#beagle]
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
Raajeshwar has quit [Ping timeout: 256 seconds]
Raajeshwar has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
<Raajeshwar>
Hi, I was working with Beaglebone AI. I could not configure pins using config-pin command. pinmux file not found! and Pin has no cape: errors are thrown. Should I change something in uEnv.txt?
<Raajeshwar>
I tried by adding "enable_uboot_cape_universal=1" in uEnv.txt which didn't work.
<Raajeshwar>
Tried to update kernel after git pull in "/opt/scripts/tools" directory and ./update_kernel.sh. This gave the following error:
<Raajeshwar>
info: checking archive
<Raajeshwar>
ERROR: The certificate of ‘rcn-ee.com’ is not trusted.
<Raajeshwar>
ERROR: The certificate of ‘rcn-ee.com’ has expired.
<rcn-ee>
@jkridner[m], do you have a beagle.cc link i can try with wget?
<rcn-ee>
ERROR: The certificate of ‘beaglev.org’ is not trusted
<zmatt>
okay, disabling the expired DST_Root_CA_X3 fixes the problem for me
<zmatt>
apparently this is a bug that affects openssl 1.0.x
<zmatt>
for sites that use a "DST Root CA X3 -> ISRG Root X1 -> R3" chain
<zmatt>
(keeping the expired cross-sign to ISRG Root X1 in the chain is apparently needed to allow websites to continue to work on Android versions older than 7.1.1)
<rcn-ee>
i was waiting for ca-certificates to update, took forever, i'll now try just updating openssl based on ^
ikarso has quit [Ping timeout: 252 seconds]
<zmatt>
updating openssl won't help
<rcn-ee>
i had a user report, that a full apt update/apt upgrade fixed it for them.. So something in the 145 updates fixed it..
<zmatt>
if the problem is missing the ISRG root (/etc/ssl/certs/ISRG_Root_X1.pem) then updating ca-certificates should fix the problem
<zmatt>
if the problem is software using libssl 1.0 instead of libssl 1.1 or something else then the fix is to either update the software (if it has been updated to use libssl 1.1) or disable/blacklist/remove the old expired DST Root CA X1
<zmatt>
(or using the "alternative chain" on server site (i.e. remove the DST Root CA X1 cross-sign), at the cost of breaking support for old Android phones)
<zmatt>
disabling the DST Root CA X1 can be done using:
<zmatt>
sudo sed -i 's/^mozilla\/DST_Root_CA_X3.crt/!mozilla\/DST_Root_CA_X3.crt/g' /etc/ca-certificates.conf && sudo update-ca-certificates
<rcn-ee>
got it, libgnutls30 made it work...: apt install --only-upgrade wget ca-certificates libssl1.1 libgnutls30
<zmatt>
I guess gnutls must have had the same issue?
<zmatt>
makes sense yeah, I see wget on debian uses libgnutls30
<zmatt>
that one-liner should fix it for any library/application that has the same problem
<rcn-ee>
correct, for any 2020.04.06 user or (earlier) release of Debian 10.x... haven't tested Debian 9.x thou..
<zmatt>
in general, what matters is having the ISRG Root X1 cert installed and the (now expired) DST Root CA X1 root removed
<rcn-ee>
correct
ikarso has joined #beagle
argonautx has quit [Ping timeout: 260 seconds]
<zmatt>
if no updated ca-certificates is available for some older release, an alternative is just manually installing the ISRG root into /usr/local/share/ca-certificates/
florian has quit [Quit: Ex-Chat]
<rcn-ee>
laughs, so the certificates don't need an update.. This is all that is needed on a fresh install: sudo apt update ; sudo apt install --only-upgrade libgnutls30
<zmatt>
I just checked the nodejs that's installed on it, but it embeds openssl 1.1.1b, not 1.0.x
<zmatt>
I'm pretty sure 1.1.1b is many security vulnerabilities ago ;P
<rcn-ee>
In bullseye, we do not have anything using the default nodejs, anything nodejs related is using https://nodejs.org/ official LTS releases.. (node-red and vscode are the only two main users by default..)
<rcn-ee>
(bonescript is gone..)
<zmatt>
we use nodesource
<rcn-ee>
yeap, nodesource is a good place to get it..
<zmatt>
not sure what you mean by "nodejs.org official LTS releases" ... nodejs.org doesn't have debian packages
<rcn-ee>
for example, in our node-red "deb" we have a local copy of nod-red's required version of nodejs, that it uses..
<zmatt>
ew
<rcn-ee>
yeah, but it allows us to run Cloud9, bonescript, and Node-RED on Stretch/Buster with each having differnet nodejs release requirements..
<rcn-ee>
(cloud9/bonescript are gone, so thank goodness.)
<zmatt>
I understand the motivation, that doesn't change the "ew" ;)
<rcn-ee>
yeah i felt dirty doing it.. burns a few MB of space..
<zmatt>
now that two of 'em are gone, can't node-red use the system nodejs or does it have obnoxiously specific version requirements?
<rcn-ee>
just looked up node-red, there minimal is v12... debian is shipping v12...
<rcn-ee>
We can start by using Debian's v12 in bullseye, but in a year, we might have to do the crap for v14...
<zmatt>
might just want to use nodesource v14 or even v16
<zmatt>
even bullseye still uses v12 ? ugh
<zmatt>
oh wow even sid still uses v12
<zmatt>
wtf
<rcn-ee>
that's why i pretty much ignore it, he just doesn't have time to really maintain it..
<zmatt>
yeah, it's why we use the nodesource debs
vd has joined #beagle
argonautx has joined #beagle
argonautx has quit [Ping timeout: 260 seconds]
argonautx has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
ikarso has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
russ has quit [Ping timeout: 252 seconds]
russ has joined #beagle
johanhenselmans has quit [Ping timeout: 252 seconds]
vd has quit [Quit: Client closed]
vd has joined #beagle
argonautx_ has joined #beagle
argonautx has quit [Ping timeout: 260 seconds]
argonautx_ has quit [Quit: Leaving]
giort has joined #beagle
otisolsen70 has quit [Quit: Leaving]
buzzmarshall has joined #beagle
giort has quit [Quit: giort]
<GenTooMan>
I can ask on debian dev about node js version changes?
<GenTooMan>
IE would you like me too
<zmatt>
I don't really care... and the answer is probably something like caring more about stability than about having the latest version (nodejs major version upgrades tend to break _everything_)