However, the systemd journal raw format is binary data and would much rather a plain text log. All things being equal I'd rather deal with human readable files.
383 karma · joined January 4, 2012
However, the systemd journal raw format is binary data and would much rather a plain text log. All things being equal I'd rather deal with human readable files.
I guess I can't have important announcements from Proton in the future if it's polluted with these low value messages.
However... "This is an X11ism, originally an xsetting 1 which frequently results is in unexpected behavior when people pressing the middle mouse button."
Does this even work on Wayland? I'm still using X11 for many reasons, including highlight/middle-click-paste.
I'm trying to recall how NVidia behaved for games, but my daily driver is an old 1050 Ti that's been rock solid for years now, also X11.
Maybe the problem is Wayland not NVidia?
What I don't get is if these are proscribed steps (and they do read as such) why are they not automated with the module install? Why are we still fighting these issues if the 'workaround' is linear and well described? Is it as flimsy a reason as "write-an-article, collect-advertising-revenue" rather than contribute code to the installer?
I don't think it's https://www.infosec.ox.ac.uk/
There's also this AI security research lab, https://lasr.plexal.com/
It looks like Oxford are quite busy in this space.
I can't quite work out who they donated to - it seems there are a number of Oxford Uni cybersec/infosec units. Any idea which one?
I'm tired of the price hikes for AI - if it was good enough without AI, it's should be optional and a separate sub. It's an enhancement not a core feature.
Personally, my opinion, I use sudo, and if I take more than 3 goes then I deserve a timeout to get my act together. Anyway, 10 attempts isn't enough to brute-force a decent password, and if bruteforcing is a concern then add 2FA codes or hardware.
There's more serious concerns in the article though - the part about the screensaver / hyprlock? That's just security theatre.
What's not cool is not pushing a fresh Docker image to secure the CVE, leaving anyone using Docker hanging. Regardless of the new policy, they should have followed through and made the fix public on all distribution channels. Leaving a known unsafe version as the last release is irresponsible.
(Edit: I misread your comment, fixed mine, I agree with you)