2 ms·

> FWIW, IMO upstream systemd should split their monolithic library and allow users to pick better that way, but this has other implications on DX. FWIW, upstre

> FWIW, IMO upstream systemd should split their monolithic library and allow users to pick better that way, but this has other implications on DX. FWIW, upstream systemd has the opinion that no-one should load the library for startup notification, instead they should use the well documented api and just write a message to a socket.

idoubtit 3y ago
Indeed, that's what the Debian maintainer of OpenSSH did soon after the quick security fix. He replaced the dependency on libsystemd with some hand-made code that notifies systemd by socket. https://salsa.debian.org/ssh-team/openssh/-/commit/cc5f37cb8405cba624a133f4b8f464fbe381c5c8 https://salsa.debian.org/ssh-team/openssh/-/commit/cc5f37cb8...
ptx 3y ago
That's not what they said in their update to the documentation[0] last week, which says that "although using libsystemd is a good choice, this protocol can also be reimplemented without external dependencies". It calls it a "good choice". Did they say somewhere else that no-one should do it despite it supposedly being a good choice? [0] https://github.com/systemd/systemd/pull/32030/files https://github.com/systemd/systemd/pull/32030/files
- klooney 3y ago
  Yes- https://mastodon.social/@pid_eins/112202696589971319 https://mastodon.social/@pid_eins/112202696589971319