systemd
throttled
systemd | throttled | |
---|---|---|
517 | 102 | |
12,516 | 2,582 | |
1.6% | - | |
10.0 | 5.1 | |
1 day ago | 5 months ago | |
C | Python | |
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
-
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
- Going in circles without a real-time clock
-
The xz sshd backdoor rabbithole goes quite a bit deeper
I find this the most plausible explanation by far:
* The highly professional outfit simply did not see teknoraver's commit to remove liblzma as standard dependency of systemd build scripts coming.
* The race was on between their compromised code and that commit. They had to win it, with as large a window as possible.
* This caused serious errors.
* The performance regression is __not__ big. It's lucky Andres caught it at all. It's also not necessarily all that simple to remove it. It's not simply a bug in a loop or some such.
* The payload of the 'hack' contains fairly easy ways for the xz hackers to update the payload. They actually used it to remove a real issue where their hackery causes issues with valgrind that might lead to discovering it, and they also used it to release 5.6.1 which rewrites significant chunks; I've as yet not read, nor know of any analysis, as to why they changed so much.
Extra info for those who don't know:
https://github.com/systemd/systemd/commit/3fc72d54132151c131...
That's a commit that changes how liblzma is a dependency of systemd. Not because the author of this commit knew anything was wrong with it. But, pretty much entirely by accident (although removing deps was part of the point of that commit), almost entirely eliminates the value of all those 2 years of hard work.
And that was with the finish line in sight for the xz hackers: On 24 feb 2024, the xz hackers release liblzma 5.6.0 which is the first fully operational compromised version. __12 days later systemd merges a commit that means it won't work__.
So now the race is on. Can they get 5.6.0 integrated into stable releases of major OSes _before_ teknoraver's commit that removes liblzma's status as direct dep of systemd?
I find it plausible that they knew about teknoraver's commit _just before_ Feb 24th 2024 (when liblzma v5.6.0 was released, the first backdoored release), and rushed to release ASAP, before doing the testing you describe. Buoyed by their efforts to add ways to update the payload which they indeed used - March 8th (after teknoraver's commit was accepted) it was used to fix the valgrind issue.
So, no, I don't find this weird, and I don't think the amateurish aspects should be taken as some sort of indication that parts of the outfit were amateuristic. As long as it's plausible that the amateuristic aspects were simply due to time pressure, it sounds like a really bad idea to make assumptions in this regard.
throttled
-
T480 - Downgrading i7 8650 to i5 8250 because of fan noise
Yes i know it sounds wild but I need to be able to focus on my programming tasks. I run linux on my system and with throttled installed, it gets noisy and i'm tired of it. I'm not a gamer but I use win10 and win11 VMs and compile source code and just every day tasks spin up this fan. Before I installed throttled ( https://github.com/erpalma/throttled ) it was out of control. I haven HP 840 G5 that hardly even spins up. I got this because i had the same one for work and noticed it never bothered me. I have compared some compile times on the i5 and the i7 and even my desktop, they are all about the same so I dont see why I should care about having an i7. Im willing to buy a new mobo with the i5 8250 and just use that. i bought the dual heatsink fan and waiting for that to arrive so i'll install that first. But can anyone else share their experience with an i5 vs i7 and fan noise?
- Possibly at the end of my Linux journey - nothing works correctly
-
How to undervolt T480 under Debian 12 using throttled?
I have a T480 with an i7-8650U and I am a little confused undervolting using throttled
-
Intel vs AMD for Linux
It's the reverse. For some reason, the embedded controller (EC) on the T480 (and other later Intel Thinkpads) is aggressive with regards to throttling the CPU clock speed even when the temperature isn't that high. To solve this, someone made a program called throttled https://github.com/erpalma/throttled to fix the issue.
-
I just bought a T480s, have some questions
Planning to install Arch (EndeavourOS) on it. In the arch wiki and these forums, thermal throttling is mentioned per this post - https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/. However this is 5yr old. Is throttling still an issue? And do you need to install throttled (https://github.com/erpalma/throttled) ?
-
Would the T480 be a good laptop for running Linux?
Thermal throttling can be tweaked through throttled.
-
Is X1 Carbon gen 6 a decent (beginner) Linux machine?
The machine throttles, under (only) Linux, when too law a CPU temperature is reached. Lenovo promised for months to fix this and then announced that it would not, after all, fix it. But the community came to the rescue.
-
Which ThinkPad model do you suggest I buy that works well with Linux?
The only thing with the X1C series though is that the thermals straight-up sucks; the laptop out of the box gets really hot really quick and throttles immediately. The first thing I did when I got it was undervolting the CPU with throttled, which helped a lot and increased my battery life significantly too. The fan basically only comes on under pretty heavy load now; before it sounded like it was about to achieve liftoff at about 20% cpu load.
- Thanks to everyone who helped out on a previous post. Got a great deal on a used X1 Carbon Gen 6 that doesn't even feel used!
-
New X1 glass touchpad and a thermal repaste
This? https://github.com/erpalma/throttled
What are some alternatives?
openrc - The OpenRC init system
KonaBess - A GPU overclock & undervolt tool for various Snapdragon chips
tini - A tiny but valid `init` for containers
thinkfan-control-gui - a small gui app for linux to control fan speed and monitor temps on a thinkpad
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
RyzenAdj - Adjust power management settings for Ryzen APUs
s6 - The s6 supervision suite.
thinkpad-e14-linux - Current state of GNU/Linux on Lenovo Thinkpad E14
earlyoom - earlyoom - Early OOM Daemon for Linux
throttlestop - Simple tool to manage thermal behaviour on Linux
supervisor - Supervisor process control system for Unix (supervisord)
bbswitch - Disable discrete graphics (currently nvidia only)