|
News News regarding BSD and related. |
|
Thread Tools | Display Modes |
|
||||
Linux's Systemd can be pwned via an evil DNS query
This is the systemd DNS service that Poettering & co. recommended to use...
https://www.theregister.co.uk/2017/0..._by_dns_query/ Some others considerations about resolvd from Andrew Ayer's blog: Quote:
__________________
The world doesn't live off jam and fancy perfumes - it lives off bread and meat and potatoes. Nothing changes. All the big fancy stuff is sloppy stuff that crashes. I don't need dancing baloney - I need stuff that works. -- Theo de Raadt |
|
|||
There are several Linux distributions that don't use systemd. For example Slackware.
|
|
||||
It was identified as being vulnerable to cache poisoning a few years ago: http://seclists.org/oss-sec/2014/q4/592
And this was a few years after publication of RFC5452 (2009). Many Linux people simply have their heads in the sand with regards to systemd and it's pretty much "bandwagon fallacy" all over again, where systemd fans are sneering at anyone who doesn't want systemd and treating the widespread adoption of shit code as "inevitable". This really proves that systemd fans aren't so different from the average windows user, who many in turn look down upon. It seems to me that some are so heavily invested in this crap that they can't easily back out and just want others to just shut up and put up and do the same, so that they can feel more at ease with their choice. The old "you don't have to use this bit or that bit" excuses from the apologists are wearing a bit thin. |
|
||||
Practically, saying code it yourself, or use something else no longer applies. RedHat is kind of the Microsoft of the Linux world and Poettering is their employee. Though various niche distributions won't use it, it's become almost impossible to avoid, at least when using Linux commercially, especially after Debian and Ubuntu went over, to avoid. Yes, you could use Slack, or Gentoo, or a few others, but generally, in the US at least, people are going to expect RedHat/CentOS and/or Debian/Ubuntu.
|
|
||||
I saw this on Twitter from Rob Graham (@ErrataRob) regarding this issue:
Quote:
|
|
||||
There is another option. Linux users can accept the bad fact and be on guard or they can stop using Linux. But you are correct in your sentiment. The time for complaining ended a few years ago. Continuing to use the system and complaining about it makes no sense. Either use it or do not.
|
|
||||
Quote:
__________________
hitest |
|
||||
This site, Without Systemd, has a large list of systemd-free Linux distributions. They also list many other Unix-like OSs, but I'm not sure if systemd is a direct threat to be ported to them or not.
|
|
||||
If you're just running Linux at home, then you can use one of the variants. If using it at work, at least in the US, the most common thing to see is CentOS. A lot of people stayed on CentOS-6 to avoid systemd, but it's getting somewhat long in the tooth. We have some CentOS-7.x machines and so far, they're not horrible. Heh, just realized that I'm writing this from a CentOS-7 machine, but this is a home workstation-cum-server where I'm not that concerned.
|
|
||||
Good question. Systemd is not in Slackware-current yet, so I think there is a better than average chance that the next stable release of Slackware will not have systemd. Therefore, Slackware will continue to be systemd free for the next 1-2 years.
__________________
hitest |
|
|||
Problem with replacing systemd is it exposes and encourages to use its non-standard interfaces. Software can be written to be systemd-dependend. Large part of FOSS community idea is to not only write, share and use freely licensed software (code), but also use openly standardized protocols (e.g. HTTP, XMPP), file formats (e.g. Open Document Format) and programming interfaces. It seems like systemd has only freely licensed code, but does not bother to meet other requirements of FOSS.
__________________
Signature: Furthermore, I consider that systemd must be destroyed. Based on Latin oratorical phrase |
|
||||
Quote:
Probably there's a positive side to this too. 7 years is a long time in computing. Lots can and will change. systemd could well be dead as a doornail by then, killed by its own demerits. Whatever good ideas it may have could be implemented differently. We'll probably all be worried about something else by then. |
|
|||
For me Slackware is missing security mitigations, so I prefer OpenBSD.
__________________
Signature: Furthermore, I consider that systemd must be destroyed. Based on Latin oratorical phrase Last edited by e1-531g; 16th July 2017 at 08:35 PM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Linux greybeards release beta of systemd-free Debian fork | comet--berkeley | Other BSD and UNIX/UNIX-like | 0 | 29th April 2016 09:47 PM |
Is OpenBSD adopting Linux's systemd? | cravuhaw2C | OpenBSD General | 8 | 19th September 2015 03:03 PM |
Stallman: Did I say Jobs was evil? I meant really evil. | J65nko | News | 1 | 30th October 2011 08:18 PM |
pftop state query. | bsdnewbie999 | OpenBSD General | 1 | 10th April 2009 03:33 AM |
Directory query | delboy | FreeBSD General | 6 | 8th September 2008 01:51 PM |