**** BEGIN LOGGING AT Tue May 03 02:59:58 2016 May 03 16:55:56 yet another openssl advisory May 03 17:02:52 we can't be the only ones binarily stuck with openssl 0.9.8 May 03 17:05:06 oh, we're lucky, RHEL 5 has openssl 0.9.8 May 03 17:05:09 and they're offering fixes until 2020 May 03 17:05:46 effort is on the way to get a new upstream for maemo May 03 17:06:08 we still have binaries with no source that link to 0.9.8 May 03 17:06:51 freemangordon pls port fixe May 03 17:06:52 s May 03 17:29:49 kerio: link? May 03 17:41:20 luke-jr: http://redhat.com LUL May 03 17:41:34 … May 03 17:41:37 to the advisory May 03 17:42:09 https://mta.openssl.org/pipermail/openssl-announce/2016-May/000072.html May 03 17:46:04 kerio: sorry, all my time ATM is dedicated to RL and linux kernel. Try to find someone else to do it. May 03 17:56:11 kerio, getting 'fixes' from redhat? LOL May 03 17:56:32 well, i'm pretty sure that they're redistributable May 03 17:58:59 and honestly i trust them with security patches for stuff like that May 03 17:59:02 it's like their job or something May 03 17:59:57 :nod: May 03 18:00:01 the thing is they backport a lot of stuff May 03 18:00:05 not just security May 03 18:00:16 well, we can't blindly apply all their patches anyway May 03 18:00:20 if it's like their kernel it's gonna be a mess May 03 18:00:34 they have openssl 0.9.8e-fips-p May 03 18:00:42 isnt redhat basically nsa? May 03 18:02:09 no May 03 18:02:42 oh, that's a good news. but really? May 03 18:03:17 really, they're not May 03 18:03:29 that's an insider info? May 03 18:04:02 afaik rh is the home of the bugs, holes and #poettering May 03 18:04:02 they're destroying linux much quicker than nsa could ever hope to May 03 19:03:53 you seen the quote? May 03 19:05:38 which one May 03 19:05:52 >>This "users are too stupid" argument is nonsense made up by big corporate software to justify continuous revenue streams based on features that get in our way. To see a smoking gun, go to This interview with Red Hat CTO, Brian Stevens, search the first occurrence of the word complexity, and read that paragraph and the one below it. That's the explanation for the explosive complexification of some realms of Linux in the past two decades. May 03 19:05:53 Those two paragraphs also provide a possible explanation when you ask why systemd came uncomfortably close to conquering the world.<< http://troubleshooters.com/linux/avoid_complexity.htm - I always said this was a root rationale for RH to pay Poettering for systemd May 03 19:09:56 add complexity to core system to a point where every commercial user will happily subscribe to enterprise level SLA with the few companies (RadHat!) that still have control over that complexity and actually are the only ones able to maintain it May 03 19:10:35 sorry typo, s/Rad/Rat/ May 03 19:12:28 while for the regular ignorant lazy devel they promise (and offer) a convenience package like "unit files are simple, we take care of all the rest" May 03 19:14:37 * DocScrutinizer05 idly wonders how many **RHEL** servers suffered that segfault-in-PID1 issue during boot that e.g. opensuse introduced dunno a year or so ago May 03 19:16:00 thinking about it that friggin bug could also have been quite welcome or even intentional May 03 19:16:34 best of all: you couldn't *shutdown* the system anymore May 03 19:17:38 nothing smaller than a powercycle needed to at least get into console May 03 19:17:55 not even via sysrq-trigger? May 03 19:18:13 those are disabled by default in systemd systems May 03 19:18:42 I mean, c'mon "that's not what user is supposed to be able to do" May 03 19:19:07 NOTABUG May 03 19:19:28 LUL May 03 19:19:47 oh well, hetzner at least has an automated powercycle May 03 19:20:12 yep May 03 19:21:27 ~nosystemd May 03 19:21:28 from memory, nosystemd is https://devuan.org http://without-systemd.org/wiki/index.php/Arguments_against_systemd http://blog.darknedgy.net/technology/2015/10/11/0/ May 03 19:22:08 Systemd Disables the Linux Magic SysRq Key - closed as "NOTABUG" May 03 19:22:28 hold on surely you can just reenable it with a sysctl or something May 03 19:23:01 well, if I knew what the fsck systemd did to disable it, to start with... May 03 19:23:53 on my machine it always been enabled, until I upgraded distro and got the gonocacacacus err sytemd pest May 03 19:24:11 i have a debian sid server May 03 19:24:16 with sysvinit May 03 19:24:42 i should migrate it to freebsd but arm is tier2, so no binaries ._. May 03 19:26:59 grab some multicore boxen and masscompile? **** ENDING LOGGING AT Wed May 04 02:59:58 2016