3 ms·
> It is a security issue The "security issue" expressed is that someone creates 4 billion lock files. The entire reason an application would have a path to cr
by cogman10 1y ago
> It is a security issue
The "security issue" expressed is that someone creates 4 billion lock files. The entire reason an application would have a path to create these lock files is because it's dealing with a shared resource. It's pretty likely that lock files wouldn't be the only route for an application to kill a system. Which is a reason why this "security issue" isn't something anyone has taken seriously.
The reason is much more transparent if you read between the lines. Systemd wants to own the "/run" folder and they don't like the idea of user space applications being able to play in their pool. Notice they don't have the same security concerns for /var/tmp, for example.
- em-bee 1y agothey don't like the idea of user space applications being able to play in their pool i think that is somewhat reasonable. but then systemd should have its own space, independent of a shared space: /var/systemd/run or /run/systemd/ ?
- overfeed 1y ago> then systemd should have its own space, independent of a shared space This would go contrary to an unstated goal: making everyone else to dance to systemd's tune, for their own good.
- simoncion 1y agoUnstated, but obvious. From a long while back: [0][1] [0] <https://lore.kernel.org/all/20140402144219.4cafbe37@gandalf.local.home/ https://lore.kernel.org/all/20140402144219.4cafbe37@gandalf....> [1] <https://lore.kernel.org/all/CA+55aFzCGQ-jk8ar4tiQEHCUoOPQzr-Mz+-LsPHCWZKryXZquQ@mail.gmail.com/ https://lore.kernel.org/all/CA+55aFzCGQ-jk8ar4tiQEHCUoOPQzr-...>