InitWare
systemd
InitWare | systemd | |
---|---|---|
19 | 518 | |
177 | 12,516 | |
0.0% | 1.6% | |
1.8 | 10.0 | |
over 2 years ago | 4 days ago | |
C | C | |
GNU Lesser General Public License v3.0 only | GNU General Public License v3.0 only |
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.
InitWare
- What do you understand under "FreeBSD way" and "Linuxism"?
-
These @rustlang ads are getting out of control.
Fear not. They get to be part of the future too.
-
Framework: Open Sourcing Our Firmware
> Yes indeed, I should've expanded to requiring user namespaces and other kernel magic I can't expect from any random box i wanna work on.
That's fair, do have to make sure to avoid to modules that do user systemd services.
Longer term, though, I am hoping https://github.com/InitWare/InitWare will help with the userland part. And I hope to personally help with things like
https://lists.freebsd.org/archives/freebsd-arch/2022-January...
https://lore.kernel.org/lkml/f8457e20-c3cc-6e56-96a4-3090d7d...
to get us more sane cross-platform system calls.
-
Preventing Log4j with Capabilities
I know, but support is still in FreeBSD. My big long term plan is:
1. Work on FreeBSD cross in Nixpkgs, because I need a way to pin forks and run nice tests without going insane. (We already have NetBSD cross.)
2. Rig up a booting image that uses https://github.com/InitWare/InitWare, the fork of systemd.
3. Add support to CloudABI in initware.
4. Bang on drum for other OSes and upstream systemd to implement this stuff we can can good portable abstractions -- I think this is our best shot to get "portable containers".
-
NixOS on Framework Laptop
I haven't bothered to have a beef with systemd, but some of us have discussed https://github.com/InitWare/InitWare to support non-Linux kernels. That would be really fun.
-
OpenBSD 7.0 Released
I'm the first to admit that I'm ignorant of the facts here, but seeing that a systemd fork ran on OpenBSD for the first time two months ago does not give me confidence that it's "an option" in the sense that you can trust it to work well.
And to be pedantic (this is an OpenBSD thread, after all), it's not "systemd", it's a fork of systemd called "InitWare", and the GitHub repo describes it as "alpha software".
Someone also pointed out in the discussion you linked that it doesn't seem to include journald. Here's a relevant PR: https://github.com/InitWare/InitWare/pull/27
-
macOS, meet SystemD: InitWare (fork of systemD) ported to macOS
The project GitHub is found at https://github.com/InitWare/InitWare
- InitWare (a systemd fork) has been ported to macOS
-
Freebsd + Gnome3 => No systemd?
You may have heard of InitWare https://github.com/InitWare/InitWare. Discussions, note that one of the titles is misleading:
- InitWare, a SystemD clone for OpenBSD
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
What are some alternatives?
rtw89 - Driver for Realtek 8852AE, an 802.11ax device
openrc - The OpenRC init system
init - KISS Linux - Init Framework
tini - A tiny but valid `init` for containers
hummingbird - Hummingbird init system for Linux based operating systems.
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
seL4 - The seL4 microkernel
s6 - The s6 supervision suite.
InitKit - Neo-InitWare is a modular, cross-platform reimplementation of the systemd init system. It is experimental.
earlyoom - earlyoom - Early OOM Daemon for Linux
libportal - libportal - Flatpak portal library
supervisor - Supervisor process control system for Unix (supervisord)