Lol, yeah I know why this is.
We have probably the same problem with dns.lightningwirelabs.com where Daniel contacted me yesterday that a system with Core Update 125 was unable to update its DNS record.
Those systems simply use an outdated version of OpenSSL and we require TLS 1.2 or better with all the bells and whistles. We might have to downgrade that to catch all fireinfo profiles.
Some really old systems will send via HTTP and we won’t upgrade them to HTTPS because the whole profile has of course already been transmitted.
Suggestions on what to do?
-Michael
On 30 Jul 2019, at 17:59, Peter Müller peter.mueller@ipfire.org wrote:
Hello *,
having a look at the Fireinfo statistics every now and then (https://fireinfo.ipfire.org/), I just noticed 41.68% of all reporting installations are running on the latest Core Update.
As far as I am concerned, that number is pleasing, but we used to have fractions of ~ 33.00% here. So, people are either installing updates faster than they did in the past (I rather doubt it) or many (heavily) outdated installations disappeared.
On the other hand, due to datacenter migration issues, we are behind the normal release schedule - thus giving admins more time to update to the current version.
Just thought you might find this interesting.
Thanks, and best regards, Peter Müller -- The road to Hades is easy to travel. -- Bion of Borysthenes