libinput-config VS systemd

I think a solution for fractional scaling is on the way for wayland. for the fingerprint you are most likely to be out of luck as i am too. my workaround is enabling autologin for my user account without typing the password although it is insecure, i fixed my touchpad scroll speed using https://gitlab.com/kirbykevinson/libinput-config. may be give them a try,

I don't think you can set it per device, bit you can see all available settings here. https://gitlab.com/kirbykevinson/libinput-config

KDE is sorted. No UI option in Gnome AFAIK, but there's a known "hack": https://gitlab.com/kirbykevinson/libinput-config (scroll-factor is what you are looking for). It's very easy to install libinput-config in Fedora Workstation; as for Silverblue it's likely that one will have to take the time to package it and then layer it with rpm-ostree install)

Yeah, that's a known problem. I had success with this: https://gitlab.com/kirbykevinson/libinput-config

There’s also this project: https://gitlab.com/kirbykevinson/libinput-config With some nifty hacks it manages to configure stuff which would otherwise not be possible to configure. Among other things, you can also configure the speed for your scroll wheel. It works absolutely fine for me.

Initially scroll speed was too high, which is a little annoying to change on Gnome. I used libinput-config and set it to 0.2 and now it feels good. This is more or less a personal configuration choice but I found the default distractingly high so thought I'd mention it.

The AUR just makes it easy to manage software outside of the arch repos. Like for instance I need libinput-config because my trackpad scroll speed is way too fast by default with libinout and gnome currently doesn't have a way to configure trackpad scroll speed so I use it to slow it down with this. Using yay and libinput-config-git to compile and install libinput-config is much faster than doing it manually and it makes it easier to remove as well. Sure I need to read the pkgbuild but most pkgbuild files are easy and digestible to read and understand.

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