systemd
earlyoom
systemd | earlyoom | |
---|---|---|
520 | 60 | |
12,552 | 2,716 | |
1.9% | - | |
10.0 | 8.6 | |
about 22 hours ago | 17 days ago | |
C | C | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
systemd
- Dlopen() Metadata for ELF Files
-
PoC to demonstrate root permission hijacking by exploiting "systemd-run"
No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.
And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.
Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.
-
Run0 – systemd based alternative to sudo announced
> 3. even `adduser` will not allow it by default
5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.
7. POSIX allows it:
* https://github.com/systemd/systemd/issues/6237#issuecomment-...
-
Systemd Rolling Out "run0" As sudo Alternative
> I for one love to type out 13 extra characters
FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.
> I wonder what random ASCII escape sequences we can send.
According to the man page source[0]:
> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`
and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.
In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.
(Happy to be shown if that's a mistaken expectation though.)
[0] https://github.com/systemd/systemd/blob/main/man/run0.xml
[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...
- Crash-only software: More than meets the eye
-
Systemd Wants to Expand to Include a Sudo Replacement
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...
-
"Run0" as a Sudo Replacement
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237
PS: https://pwnies.com/systemd-bugs/
-
Linux fu: getting started with systemd
https://github.com/systemd/systemd/issues/32028#issuecomment...
There are some very compelling arguments made there if you care to read them
-
Ubuntu 24.04 (and Debian) removed libsystemd from SSH server dependencies
Maybe it was because you weren't pointing out anything new?
There was a pull request to stop linking libzma to systemd before the attack even took place
https://github.com/systemd/systemd/pull/31550
This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.
-
Systemd minimizing required dependencies for libsystemd
The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.
https://github.com/systemd/systemd/pull/31550
earlyoom
- Earlyoom – Early OOM Daemon for Linux
- Fedora Workstation 39
-
earlyoom VS thrash-protect - a user suggested alternative
2 projects | 12 Oct 2023
-
Linuxatemyram.com
> The system is not supposed to 'lock up' when you run out of physical RAM. If it does, something is wrong. It might become slower as pages are flushed to disk but it shouldn't be terrible unless you are really constrained and thrashing. If the Kernel still can't allocate memory, you should expect the OOMKiller to start removing processes. It should not just 'lock up'. Something is wrong.
I don't why but locking up is my usual experience for Desktop Linux for many years and distros, and I remember seeing at least one article explaining why. The only real solution is calling the OOMKiller early either with a daemon or SysRq.
> It should not take minutes. Should happen really quickly once thresholds are reached and allocations are attempted. What is probably happening is that the system has not run out of memory just yet but it is very close and is busy thrashing the swap. If this is happening frequently you may need to adjust your settings (vm.overcommit, vm.admin_reserve_kbytes, etc). Or even deploy something like EarlyOOM (https://github.com/rfjakob/earlyoom). Or you might just need more RAM, honestly.
Yeah. Exactly. But as the thread says, why aren't those things set up automatically?
- OOM still a disaster zone
-
Fedora spins
It's not that simple: some defaults may differ, and some features may arrive at different times (if ever). For example, earlyoom has been enabled on Workstation since F32, but the KDE Plasma spin got it one release later.
-
So what exactly do I do if Linux crashes?
Most answers will answer your question, but you can do better and avoid the freezes in the first place. IME almost every time the system froze up and didn't come back in a few seconds it was out of memory. The obvious solution is to add memory, but you can use Early OOM to kill hungry processes if you're running out of memory instead.
- Why is there no reliable way to receive signal when OOM killer decides to kill you
-
What do you do when Linux becomes unresponsive (in a frozen state,mouse clicks or keyboard doesn't work)
It sounds like you're running out of memory though, so if your OS's OOM killer isn't working as well as it should, you can try earlyoom as an alternative.
-
Linux Desktop Environments System Usage (Gnome, KDE, XFCE, LXQT, Cinnamon, Mate)
Swap is indeed supposed to prevent this AFAIK. You can though try some tools like EarlyOOM and see if it helps : https://github.com/rfjakob/earlyoom
What are some alternatives?
openrc - The OpenRC init system
oomd - A userspace out-of-memory killer
tini - A tiny but valid `init` for containers
nohang - A sophisticated low memory handler for Linux
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
darling - Darwin/macOS emulation layer for Linux
s6 - The s6 supervision suite.
XMousePasteBlock - Userspace tool to disable middle mouse button paste in Xorg
supervisor - Supervisor process control system for Unix (supervisord)
le9-patch - [PATCH] mm: Protect the working set under memory pressure to prevent thrashing, avoid high latency and prevent livelock in near-OOM conditions
dracut - dracut the event driven initramfs infrastructure
ZenStates-Linux - Dynamically edit AMD Ryzen processor P-States