I'll bet that Linux purists will like this one. :)
"A buffer overflow vulnerability in the dhcp6 client of systemd allows a malicious dhcp6 server to overwrite heap memory in systemd-networkd. Affected releases are systemd: versions up to and including 239."
@hund systemd-networkd again, isn't it?
IMO systemd does a pretty good job as init, but there's no reason to replace pre-existing network configuration software with systemd-networkd and systemd-resolved.
It's sad that some distros do it.
@Wolf480pl I'm really trying to like Systemd, but they're making it hard for me, even before this incident.
That said, they could reuse existing DHCP clients etc...
Personally, I would never use systemd for anything but init, where it actually does a pretty good job.
If they're trying to unify the way of configuring network across distros, they're doing something wrong.
Or rather: they want the wrong thing.
First of all, unlike with init scripts, there's no reason for network config to be done by anyone else than the admin of a particular machine.
So it has nothing to do with upstream, and everything to do with people who use a particular distro on the machines they administrate (be it their own or their employers').
Then, the very purpose of having multiple distros is that people disagree about how things should be done, and they choose a distro that is most aligned with their vision.
So different distros have different network configuration schemes _because_ their users have different needs and desires.
Therefore it's impossible to have one way of configuring network that will satisfy everyone.
And as I said before, there's no gain from an unified way.
No gain, only harm => no point.
But like everything else in Linux, that doesn't matter. I know for a fact there are places with mixed distros. Perhaps the admins there prefer a single but not perfect system over multiple other, also not perfect, systems?
I don't know. I'm with you on this one. But saying they're doing it wrong might be taking it too far; it depends on their goals, doesn't it?
Dunno, but one of the first things I did after joining a team of sysadmins taking care of a number of servers, all with different distros, was picking one distro that:
- everyone knows
- is good enough for the job
and start transitioning everything to it.
I haven't yet seen a case where having multiple distros within one server fleet was beneficial, yet having a common network config format on all of them wouldn't counteract that benefit.
@hund oh great! Just one more reason people will love systemd
Linux Geeks doing what Linux Geeks do..