3 ms·

It's present on loads of systems, it's a very common service to offer, it's a reasonably well-constrained use case, and the fact that nobody thinks about it mig

by luma 2y ago

It's present on loads of systems, it's a very common service to offer, it's a reasonably well-constrained use case, and the fact that nobody thinks about it might be a good reason to think about it. They can't boil the ocean but one service at a time is a reasonable approach. I'll flip the question around, why not start at ntpd?

cogman10 2y ago
> I'll flip the question around, why not start at ntpd? Easy, because there are loads of critical infrastructure written in C++ that is commonly executed on pretty much every VM and exposed in such a way that vulnerabilities are disasterous. For example, JEMalloc is used by nearly every app compiled in *nix. Perhaps systemd which is just about everywhere running everything. Maybe sshd, heaven knows it's been the root of many attacks.
- hedora 2y ago
  There’s a nice pure-rust ssh client/server already. Systemd should just be scrapped. This week’s wtf “systemd-tmpfile —-purge” intentionally changed its behavior to “rm -rf /home”. Confirmed not-a-bug. There are dozens of other comparable screwups in that stack, even ignoring the long list of CVEs (including dns and ntp, I think). Rust can’t fix that. I haven’t heard of any issues with jemalloc, though that seems reasonable (assuming calling rust from C doesn’t break compiler inlining, etc).
  - forbiddenlake 2y ago
    > Confirmed not-a-bug. Initially closed not a bug, but then Poettering overruled that decision and implemented a fix which is already released. https://github.com/systemd/systemd/commit/e76015738942246db70f444b3567afd1b132f824 https://github.com/systemd/systemd/commit/e76015738942246db7...
  - yjftsjthsd-h 2y ago
    > There’s a nice pure-rust ssh client/server already. Prod ready, audited, non-buggy in actual use? And if so, do you have a link so I can start test-deploying it?
- kelnos 2y ago
  > For example, JEMalloc is used by nearly every app compiled in nix.* JEmalloc is used by very very very few apps compiled for *nix. That's a conscious decision that an app developer needs to make (and few would bother without specialized needs) or a distro packager needs to shoehorn into their package builds (which most/all would not do).

by luma 2y ago

cogman10 2y ago

> I'll flip the question around, why not start at ntpd? Easy, because there are loads of critical infrastructure written in C++ that is commonly executed on pretty much every VM and exposed in such a way that vulnerabilities are disasterous. For example, JEMalloc is used by nearly every app compiled in *nix. Perhaps systemd which is just about everywhere running everything. Maybe sshd, heaven knows it's been the root of many attacks.

hedora 2y ago
There’s a nice pure-rust ssh client/server already. Systemd should just be scrapped. This week’s wtf “systemd-tmpfile —-purge” intentionally changed its behavior to “rm -rf /home”. Confirmed not-a-bug. There are dozens of other comparable screwups in that stack, even ignoring the long list of CVEs (including dns and ntp, I think). Rust can’t fix that. I haven’t heard of any issues with jemalloc, though that seems reasonable (assuming calling rust from C doesn’t break compiler inlining, etc).
- forbiddenlake 2y ago
  > Confirmed not-a-bug. Initially closed not a bug, but then Poettering overruled that decision and implemented a fix which is already released. https://github.com/systemd/systemd/commit/e76015738942246db70f444b3567afd1b132f824 https://github.com/systemd/systemd/commit/e76015738942246db7...
- yjftsjthsd-h 2y ago
  > There’s a nice pure-rust ssh client/server already. Prod ready, audited, non-buggy in actual use? And if so, do you have a link so I can start test-deploying it?
kelnos 2y ago
> For example, JEMalloc is used by nearly every app compiled in nix.* JEmalloc is used by very very very few apps compiled for *nix. That's a conscious decision that an app developer needs to make (and few would bother without specialized needs) or a distro packager needs to shoehorn into their package builds (which most/all would not do).