Skip Navigation

NekkoDroid

@ NekkoDroid @programming.dev

Posts
0
Comments
57
Joined
3 yr. ago

  • Deleted

    Spotify quietly moves lyrics behind a paywall.

    Jump

  • But the funny thing is that even with a larger user base, Spotify has NEVER posted a profit

    I honestly doubt if you'd isolate Apple Music it'd be any different for them.

  • Deleted

    Spotify quietly moves lyrics behind a paywall.

    Jump

  • Lossless is pointless

    I wouldn't say its pointless, but it really doesn't help much considering the quality of your average headset/earpieces.

  • Microsoft won't fix Windows 0x80070643 errors, manual fix required

    Jump

  • It’s incredibly easy to fuck your partitions to hell and back, especially through Windows.

    Fun fact: Windows won't allow you to delete any EFI partition (that is the only one I know of/tried) unless its through diskpart with a specific override/force option.

    But then again, I somehow nuked my recovery partition by accident at some point as well.

  • Microsoft won't fix Windows 0x80070643 errors, manual fix required

    Jump

  • bless the drive with a boot loader that doesn’t suck, like Grub

    Ah yes, I need a whole separate OS just to boot my actual OS...

    I would in no world call GRUB a bootloader that doesn't suck.

  • systemd Rolling Out "run0" As sudo Alternative

    Jump

  • Basically. systemd-run was already able to do it, all that really changed is the interface for it. The change to run.c in the patch itself was <400LOC, and the entire patch was <1.4k lines with most being docs, tests and utils for coloring the terminal.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • I don’t understand how this is any improvement over pkexec

    That has the same problem as sudo: the SUID bit is set for it.

    The fact that run0 uses polkit is more of a byproduct that this kinda authentication is already done with polkit all over the place in systemd. You can have individual subcommand accessible to different users (for example everyone can systemctl status, but systemctl reboot needs to be in the wheel group) which is why its generally used within systemd already. And it wouldn't surprise me if again you can do it with this as well, limiting what commands can unconditionally run, need prompt or are completely blocked.

  • systemd Rolling Out "run0" As sudo Alternative

    Jump

  • systemd Rolling Out "run0" As sudo Alternative

    Jump

  • As the other comment said, no. But I've had the idea and will to at some point write a edit script (that I can just set EDITOR= to) that would just choose one of the first common editors. That could in theory have a -0 option to run as root (there also probably looking through run0, doas, sudo and su). Not the editor, but doing the editing on a temp file and then copying with root

  • Systemd wants to expand to include a sudo replacement

    Jump

  • I don't know, unless I personally allow the admin to have that kinda access to my files I wouldn't really want it. And for that case you can enroll recovery keys (which would need to be manually stored, but still) or a fido token or whatever other supported mechanism there is, its LUKS2 backed encryption after all. Then there is also the possibility to just not encrypt the home directory at all.

  • Systemd wants to expand to include a sudo replacement

    Jump
    1. The attack surface is there either way, this is just functionality repackaged that existed already before (systemd-run, which is calling into PID1)
    2. all compression libraries (actually most libraries at this point) are dlopened on demand (which was planned even before the attack, which is speculated that the attack was accelerated in timeline because he was on a timer before the change was released)

  • How RCS on iPhone Will Make Texting Better for Everyone

    Jump

  • Sure, the other option is having it tied to an email, which is reliant on your single vendor and is also an easier way to create an army of spam bots. Phone numbers at least are transferable between carriers.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • I guess my interpretation was too charitable.

    Nothing in the protocol prevents you from splitting the server from the window manager, just everyone implementing the wayland server protocol didn't see any benefit in splitting it out.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • I think what they meant is that there are people that think: "Wayland is too fragmented, there should be 1 'Wayland Compositor' and the rest should be window managers"

  • Systemd wants to expand to include a sudo replacement

    Jump

  • This isn't exactly a "new" attack surface, so removing the attack surface that sudo (and alternatives) is, is probably a net positive.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • it does its authorization with polkit (which IIRC defaults to allow all wheel group members) and giving users that shouldn't be allowed root access, root access, is not something you ever want. This is usually referred to as unauthorized privilege escalation. Also, it isn't like sudo doesn't need configuration.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • One way to notice a person has "systemd derangement syndrome" is by looking at how they write systemd: if they write it SystemD they are already in late stages of SDS and it isn't curable anymore.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • homed isn't exactly a home directory replacement, more of an extension. You can mix and match homed and normal home directories like you want (on a per-user basis at least, not within a single user). It does have some nice things, such as user-password based encryption of the home directory, so the password is required to unlock it (no admin access) or automatically using subvolumes on btrfs.

  • Systemd wants to expand to include a sudo replacement

    Jump

  • The thing with this is: its just a symlink to the systemd-run binary, which talks to PID1 to spawn new processes (in separate cgroups IIRC). Its one of the most fundamental parts of systemd. Even the debian systemd package includes systemd-run.

    I guess the other question is if some tools the distro provides might switch to supporting it by default. For example on Arch there is makepkg that should never be executed as root, but does internally call some things with elevated privileges (mostly pacman to install and remove packages). Currently it checks for sudo and if not falls back to su, but maybe it might be worth considering changing su for run0 if its guaranteed to be there.

  • Deleted

    GNOME Foundation in financial trouble – OSnews

    Jump

  • You should see the comments on the Phoronix forums...