No, this is not about the internet. It’s about the inxi system information reporting script. Most distros, maybe all, package it. Some include it in a default installation. It’s never been automatically installed in any openSUSE here. Current upstream is 3.0.34. TW currently has 3.0.32. Leap has a seriously ancient 2.3.40. Upstream devel version instead of being a different branch version is differently named pinxi, currently 3.0.34-01.
Each has a self update switch -U. On openSUSE, it somewhat routinely fails at SSL verification/legitmacy of the server, both for the packaged versions, and both of upstream’s latest, determined by using option “-dbg 1” in pinxi. Part of the error message points to troubleshooting the failure, but that’s over my head.
There seems to be no rhyme or reason whether failures occur, but failures persist on any given installation for hours or days at a time. The openSUSE packages prohibit -U, but this I override via /etc/[p]inxi.conf with a line B_ALLOW_UPDATE=true. Upstream is blaming the failure on openSUSE configuration.
Before I try filing a B.O.O. bug, I’d like to know whether this happens to others than myself. I have lots of openSUSE installations going all the way back to SuSE 8.2, so “myself” isn’t just me, but a lot of different PCs and installations including TW, 15.0 & 15.1. How about others here? You too getting this if you try pinxi -U? In order to test, you may need an older version to upgrade from. This could be done by extracting the 3.0.32 script from the TW rpm and putting it in /usr/local/bin or ~/bin.