systemd
freebsd-src
systemd | freebsd-src | |
---|---|---|
518 | 133 | |
12,516 | 7,490 | |
1.6% | 0.6% | |
10.0 | 10.0 | |
2 days ago | about 7 hours ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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
-
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
- Going in circles without a real-time clock
freebsd-src
- You shouldn't run a BSD on a PC
- Linux Crisis Tools
- What about the vfs.zfs.bclone_enabled sysctl now?
-
Personal FreeBSD PKGBASE Update Server
2023-06-26: https://github.com/freebsd/freebsd-src/commit/ee0aa1ce12b3caea34477a31e9d2111a329e33b9 to main (tagged release/14.0.0).
- What version of ZFS at FreeBSD solves the block cloning issue?
-
Installing FreeBSD 14 Stable on an T480 Laptop w/ an Encrypted Home Directory
It's not yet in FreeBSD base so if you want to test it you'll have to use the patch from the PR: https://github.com/freebsd/freebsd-src/pull/881
-
FreeBSD 14.0 Delivering Great Performance Uplift
Lots of great work by many people. But I bet this guy and his optimizations to the vfs and locking has made a significant impact.
https://github.com/freebsd/freebsd-src/commits?author=mjguzi...
-
ZFS 2.2.1: Block Cloning disabled due to data corruption
and then there were deep concerns about the stability of same, so vfs.zfs.bclone_enabled = 0 was left in-place
https://github.com/freebsd/freebsd-src/commit/068913e4ba3dd9...
-
FreeBSD 14.0-Release Announcement
Well there are some examples:
https://github.com/freebsd/freebsd-src/tree/main/share/examp...
But yeah that pf.conf could be expanded allot, but there are many source to cobble a conf together. My conf is massive but 99.9% commented out so i have my "template" for nearly everything, from mail to web to blacklistd etc.
-
Git cherry-pick and revert use 3-way merge
The BSD version is sort of very recent, for what it's worth -- FreeBSD imported a not fully functional version in 2017 and has seen more work on it in 2022: https://github.com/freebsd/freebsd-src/commits/main/usr.bin/... , but the default version shipped is still GNU diff3: https://man.freebsd.org/cgi/man.cgi?query=diff3&apropos=0&se... .
What are some alternatives?
openrc - The OpenRC init system
podman - Podman: A tool for managing OCI containers and pods.
tini - A tiny but valid `init` for containers
musl - unofficial musl mirror git://git.musl-libc.org/musl
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
darwin-xnu - Legacy mirror of Darwin Kernel. Replaced by https://github.com/apple-oss-distributions/xnu
s6 - The s6 supervision suite.
src - Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
earlyoom - earlyoom - Early OOM Daemon for Linux
coreutils - upstream mirror
supervisor - Supervisor process control system for Unix (supervisord)
rss-proxy - RSS-proxy allows you to do create an RSS or ATOM feed of almost any website, just by analyzing just the static HTML structure.