weywot VS systemd

WeyWot's GitHub has many great guides ( https://github.com/spxak1/weywot )

So you press F9 or F12 and boot from the bios selection ? No problems that is the easiest method, and recommended, but if your having problems you could try this https://www.youtube.com/watch?v=4idr6sXSue0&list=PLS_d8s-cLQwWWLePiVWve1X-_YP6YrwRU&index=10 this is rEFInd easy to setup and maybe it will solve your boot problem, then you will know it is something to do with the Bios boot, and lastly, probably the most difficult duel boot is editing the systemd bootloader of Pop_OS https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md approach with caution, you could lose the ability to boot either system if you make a mistake.

Das schon mal ausprobiert: https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md ?

Please check this

I currently am trying to dual boot pop os and windows. I have them in separate drives. Yesterday I was following the steps provided by this GitHub https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md. After running windows though the systemd option disappeared from my boot menu. I booted into a live disk to try and see if I could find the drive but only my drive with windows shows up. What do I do?

Refer this

Don’t throw windows out, it can be useful, I’d recommend dual booting. For the distro, I’d go with Fedora (Workstation) or PopOS. Fedora’s hard to break and reliable as well as easy to dual boot (guide) while PopOS is Ubuntu based so it can draw from Ubuntu’s giant popularity, but it’s not the easiest to dual boot (guide)

Using a more sophisticated method, like ed2k is preferred if you can. There is also this.

In many guides and other post I see people copying the EFI Windows folder similar to this github on a boot partition of approximately 1GB. But the arch wiki recommends installing the package ed2k and mapping a script to boot directly from the Windows EFI.

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.

> 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-...

> 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...

bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...

the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237

PS: https://pwnies.com/systemd-bugs/

https://github.com/systemd/systemd/issues/32028#issuecomment...

There are some very compelling arguments made there if you care to read them

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.

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