Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Out-of-bounds write in systemd-resolved with crafted TCP payload

openwall.com

Post reply on HN
Print view View original

11–20 of 26 posts

Re: Out-of-bounds write in systemd-resolved with crafted TCP payload

#11

Post by dogecoinbase »

stepik777 wrote: post #9
pjc50 wrote: post #8

Earlier quoted context omitted.

Anything Internet-facing has to accept any kind of packet without crashing, or at least without failing in an exploitable way. That's the bare minimum you-must-be-this-tall entry requirement of security.

I believe it was a joke about how Lennart Poettering usually responds to bug reports.

You are correct. See, for example, his recent response to the issue where systemd starts processes belonging to users whose usernames begin with a digit with root privileges: https://github.com/systemd/systemd/issues/6237#issuecomment-...

My deepest apologies to HN for the overly-dry sense of humor.

Re: Out-of-bounds write in systemd-resolved with crafted TCP payload

#12

Post by na85 »

stepik777 wrote: post #3

Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?

Because Poettering and his fanboys like it, and nobody's implemented anything sufficiently better to overcome the political sway of the freedesktop.org crowd.

Re: Out-of-bounds write in systemd-resolved with crafted TCP payload

#13

Post by adekok »

stepik777 wrote: post #3

Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?

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 payload

#16

Post by peterwwillis »

dogecoinbase wrote: post #11
stepik777 wrote: post #9

Earlier quoted context omitted.

I believe it was a joke about how Lennart Poettering usually responds to bug reports.

You are correct. See, for example, his recent response to the issue where systemd starts processes belonging to users whose usernames begin with a digit with root privileges: https://github.com/systemd/systemd/issues/6237#issuecomment-... My deepest apologies to HN for the overly-dry sense of humor.

Trolling on HN really is like shooting fish in a barrel, isn't it?

Re: Out-of-bounds write in systemd-resolved with crafted TCP payload

#17

Post by drdaeman »

fidget wrote: post #14
stepik777 wrote: post #3

Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?

Yeah, we really should rewrite the kernel.

Was already done, many times. Device drivers is the issue it never took off.

Re: Out-of-bounds write in systemd-resolved with crafted TCP payload

#20

Post by flyovercow »

adekok wrote: post #13
stepik777 wrote: post #3

Remind me, why are such critical system components as systemd are still being written in a memory unsafe language?

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.

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
Post reply on HN