3 ms·
Most security features which try to lock things down properly, especially when doing no-access-by-default, cause problems in unforeseen cases. I don't think it
by ealexhudson 8y ago
Most security features which try to lock things down properly, especially when doing no-access-by-default, cause problems in unforeseen cases.
I don't think it's dangerous to develop better implementations that improve security, even if they go wrong occasionally. Feels more dangerous to me shooting down the attempts of people trying to raise the security bar.
- simion314 8y agoI prefer Linus philosophy of not breaking userspace, so they should try finding a solution that is not breaking things(I assume someone will comment that is impossible in this case, add an attempt to prove/motivate it)
- LukeShu 8y agoThings are broken in this case because of a bug, not because of design decisions. All of the features "locking things down" are opt-in in the service file (to avoid "breaking userspace"), and the service file for systemd-timesyncd opted-in.
- qu4z-2 8y agoThe "bug" being systemd making all sorts of undocumented assumptions about the environment it's running it?