Gnome has defaulted to Wayland for a long time, so it sounded more like you had an issue with a different desktop environment, not X11 vs Wayland

Gnome isn’t orthogonal to Wayland.

You’d need to check if you were using the X11 or Wayland session of Gnome

I would generally just set the RPATH to $ORIGIN in the ELF file

lsof just reads from /proc and gives you formatted output

https://github.com/lsof-org/lsof/blob/master/lib/dialects/linux/dproc.c#L297

You should probably enable debian-security at least…

They’re on 6.12.101

I will say the Rust stdlib seems to make TOCTOU bugs really easy to make for filesystem operations

But, yes, Ubuntu switching to a test project hurts it

BSDs are also monolithic kernels, just like Linux, macOS, and Windows NT

FreeBSD has been trying to make it easier to run as a desktop OS by supporting the Linux APIs so they can use the WiFi and Graphics drivers from Linux

OpenBSD handles security by supporting fewer features. E.g. they do not support Bluetooth as it’s an insecure protocol, and they disabled SMT due to the hardware bugs in AMD/Intel/ARM - so they are more secure, but slower

They’re specifically talking about drones that are fly-by-wire

I don’t think anyone has invented a fiber optic cable with enough strength to stay attached for miles

While useful, you do have to be very close to the target to use this

Edit: to be clear, this advice is specific to Ubuntu. If you come across this and need advice for a different distro, message me or reply to this

Yes.

Ubuntu doesn’t follow upstream kernels, so they will have to make a custom backport for 6.17 to fix the kernel

It’s very unlikely you need the module that has the bug, so the mitigation should work for you

Just double check lsmod | grep aead

As long as that module is not loaded, and you have the kmod update that adds /etc/modprobe.d/disable-algif.conf you’re protected

The kmod change makes it so the affected module cannot be loaded, it was their initial workaround

Wait. So the flaw was in uutils, and this article reported it as a systemd bug…?

I think it’s more a finance bro psyop… “Don’t worry about the shit he’s doing, just keep investing, he’ll give up anyway”

Debian on my personal computers and servers.

Ubuntu on my work desktop, RHEL on work’s servers

I wouldn’t consider Debian “Canonical”-y, it’s just what they happened to pick as their upstream.

I tried some of the atomic distros, but ran into too many problems. When I buy a new computer, I sometimes have to run Opensuse Tumbleweed or Arch to get new enough hardware support… Too lazy to rebuild my kernel and mesa at home

Protecting its mother’s spine?

I didn’t take it as gluttonous, more just making fun of how good cat’s internal clocks are… They know what time they were fed yesterday and will remind you if you’re even a minute late

The software manager they’re using already looks like GNOME 3+

Why do people keep referencing this like it was merged…

It was specifically rejected

Maybe to help, you can see where you’ve enabled “repositories” that APT can download from in /etc/apt/sources.list and /etc/apt/sources.list.d

As long as you haven’t manually installed a .dpkg package, or manually modified it, they should be something like

deb.debian.org security.debian.org

Some things like Slack may try to add their own repositories down there

When you type “sudo apt install” it is allowed to install from any configured repos down there

The current Hegseth administration has also removed the requirements for Right to Repair from DOD contracts, so Lockheed can charge as many millions as they want on repairs