[–] 2 points 6 days ago

Most don't have hibernate enabled because you'd need a swap or swapfile large enough to hold the full memory state. And with the larger ram sizes and sleep being good enough, at least until everything became s2idle only, no one wanted to set up a huge chunk of unusable disk for it.

  • source
  • parent
  • context
  • [–] 19 points 6 days ago

    There's also situations where you want the computer to be truly off (without loosing your open documents etc), to the point where you can take out the battery and it's no big deal.

    Also, for work my fancy new computer has fancy new "modern suspend", which isn't actually suspend at all. The fan is still spinning and it's generating lots of heat. Not great in backpacks and certainly not great in industrial field work where there are areas where non rated powered electronics are not allowed due to potential explosive atmosphere.

    Meanwhile hibernate is still hibernate. The computer is actually fully powered down.

  • source
  • parent
  • context
  • [–] 5 points 6 days ago (1 child)

    I hadn't really thought about the fact that Ubuntu (and many others, apparently) don't have hibernation. I switched to Debian about a year ago, and I wasn't sure what the Hibernate button did when I saw it for the first time. But after I searched to find out, I started using it all the time.

  • source
  • [–] 1 point 6 days ago

    Maybe depends for the configs, in my case I need to build the external modules with the same compiler, and in lkml you can see a few warnings about do not mix the compiles: https://lkml.iu.edu/hypermail/linux/kernel/2107.3/08102.html

    For rust modules you need to use LVM=1 because you need to use all the LVM stack instead of the GCC stack, if I define in the Makefike the LVM=1 then the build fails with a lot of clang: error: unknown argument: ...

    So for me is impossible to build my rust modules for a kernel build with a GCC kernel

  • source
  • parent
  • context
  • [–] 11 points 6 days ago

    The article sounds a bit sloppy.
    In general this is a pretty low risk exploit. Can be used for trolling, but not to steal data or get rce.

    The freed memory can be read again as the child socket is constructed, which leads to a use‑after‑free that can trigger a kernel crash or a denial of service. The vulnerability does not directly leak data.

    https://app.opencve.io/cve/CVE-2026-98432

    The only mention I see of things beyond that are claims of rce on systems with multi-path tcp, which is rare.
    This sounds like another overblown ai-company-discovered vulnerability. They have every reason to disclose poorly and create the biggest possible fear. Even the php exploit, which was a lot worse than this, still had way more publicity and fear than it deserved.

  • source
  • [–] 18 points 6 days ago

    This is why I don't take Ubuntu seriously. They just take whatever is the latest kernel when they release the next Ubuntu version regardless of whether it is a LTS kernel or not. Which means they often end up with an upstream EOL kernel they themselves have to backport patches to for years, which in turn lead to delays like this. It's not going to get any better going forward.

  • source
  • [–] [S] 1 point 1 week ago

    To be fair, a lot of server distros have systemd. So, maybe Alpine since it has OpenRC? However it has musl instead of glibc so that might be a problem depending of your use case.

    Though cannot think of anything really, breaking after reboot says it's most likely software related. But why would that happen, no idea.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago

    Integrity verification and immutability doesn't need to be implemented through attestation. Attestation is a horrible concept used by companies to dictate you what you can and what you can not use on your hardware.

    Attestation has nothing to do with security.

    First, because attestation doesn't enforce any security standards by default, it just requires an "official" hardware-software stack. It may be used for such enforcement, but no one gives a shit, including Google with their Play Integrity Protection that allows immensely outdated devices to be accepted as "secure".

    Second, because one leaked key, and all the devices signed with that key immediately become a security circus. Yes, eMudhra way.

    Banking software

    Banking software is an absolutely horrible thing both security-wise and privacy-wise. Having it on Linux is exactly the opposite of what Linux needs.

    Do we have a choice?

    Yes. Do not use anti-consumer tech. Do not use services that require such anti-consumer tech. Demand from your banks and your government support for open technologies and standards (literally W3C-compliant web browsers are enough for practically anything).

    I do realize that it's extremely difficult and barely possible at all. But bringing that crap to open ecosystems is not the answer.

  • source
  • parent
  • context
  • view more: ‹ prev next ›