Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by stepik777 on Monday July 03, 2017 @04:15PM
(#14691056)
Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?
[ Parent
| on HN ]
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by jancsika on Monday July 03, 2017 @04:40PM
(#14691202)
I'd love to learn Rust by opportunistically implementing parts of the systemd API.
If any Rustafarians start such an effort, please make some noise about it.
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by fl0wenol on Monday July 03, 2017 @05:11PM
(#14691426)
Because if it's good enough for OpenBSD, then it's good enough for us.
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by adekok on Monday July 03, 2017 @05:30PM
(#14691545)
Because of the many years of development already put into them?
Re-writing things in a memory safe language takes a lot of time. And that's even if the language is stable and available cross-platform.
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by flyovercow on Monday July 03, 2017 @06:45PM
(#14692019)
Systemd itself invalidated the many years of design put into Unix so yeah. Bsd doesn't have this problem because bsd didn't adopt systemd
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by paulddraper on Tuesday July 04, 2017 @12:59AM
(#14693641)
Because all other languages have higher overhead or are less stable.
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by fidget on Monday July 03, 2017 @05:47PM
(#14691654)
Yeah, we really should rewrite the kernel.
Re:Out-of-bounds write in systemd-resolved with crafted TCP ...
by digi_owl on Tuesday July 04, 2017 @12:59PM
(#14696968)
Err, that is not an excuse. That just leads to the question of why there is a second kernel metastasizing in userspace.