

Also kernel 6.12 has support until 2035, so it’s not like anyone running these CPUs would be missing out on security updates for a while.


Also kernel 6.12 has support until 2035, so it’s not like anyone running these CPUs would be missing out on security updates for a while.


They’re talking about the battery percentage, not porting their phone number.
You are talking about blocks as physical delineations in an ssd, containing many pages with erase cycles. Op is talking about the filesystem view of blocks, which is different altogether.
I’m pretty sure OP is confused themselves, but I read this as referring to the physical sector size.
I’m not sure what this means, pages are a concept in an ssd’s physical structure, they don’t mean anything to a filesystem (except in volatile memory).
Fair enough, I probably explained it poorly. The problem is that pages don’t mean anything to the filesystem, but the way the filesystem is layed out means a lot to the pages. With 512e, the SSD has to buffer each write until it can make up the whole 4K page. It’ll also buffer a read until the whole 4K page is read. So if those buffers never become full/read, such as when the filesystem isn’t aligned to it’s pages, or the read/writes aren’t in the right sequence, then it destroys your performance.
This also happens with HDDs, but they’re slow enough to be able to rearrange operations, though an unaligned filesystem will still cause unnecessary reads before writes.
Do not worry about emulated block size, because ssds only use that to report to the filesystem, no sectors exist on solid state media.
Well SSDs have flash pages, which are essentially sectors as they are the smallest unit you can read/write, and they’re usually 4096 bytes on NAND flash. My understanding is to write to a flash page you have to erase the whole block of 32+ pages before writing, so if a 512e SSD doesn’t receive the rest of the page in time (e.g. with IO scheduling, 512 byte fs sectors, unaligned partitions, or bad luck), then the controller has to do a read-erase-program across the whole block of pages (although wear leveling will probably read + copy the modified page to elsewhere instead), instead of just a single program operation on one page (assuming a properly trimmed SSD).
So IMO, 4Kn is more important on SSDs, yet every vendor sets 512e by default. Luckily quite a few NVMe SSDs (not Samsung), let you change the logical block size with an nvme format command.
But more related to the OP, HDDs are a lot slower and don’t have to erase multiple sectors before a write, so it’s not as important, however partition alignment is still important but usually handled automatically in every modern partitioning tool. Sometimes you can switch a HDD to 4Kn with hdparm, but this isn’t common, and you’ve said your HDD is dead anyway, so it won’t help.
Also, sorry about bringing you into this, I have strong opinions against 512e SSDs haha.


Just be careful, I think I got a fake. I noticed the firmware was out of date, so I tried the Intel SSD update tool, which errored out with “Please contact Intel Customer Support for further assistance”. Now the SSD no longer mounts and puts a bunch of nvme errors in the dmesg.


It’ll go to the lock screen and eventually go dark. RDP (on Windows) doesn’t let you share screens/controls, AFAIK.


I believe Fwupd can also update your Secure Boot certificates.
Also, a backdoor in this particular program can steal your PGP keys.
Now you can make that decision. Evolution is also available from the Debian and Arch (and others) repos without sandboxing, if you’d prefer it to have access your whole system.
You can also remove those permissions with the Flatpak cli, or Flatseal.
It’s in no way like Android where “OpenKeychain” were forced to define a protocol and now reading a key prompts the user.
I don’t see why this couldn’t be done with Secret Service, just no one does so no one expects it. You should email one of the mailing lists for GnuPG if this bothers you though.
Oh, and one of the few dozen local privilege escalations found by AI in the mountains of trash of our great kernel completely negate all of this.
Well yeah, sandboxing/containers/namespaces were never guaranteed to be fully isolated, there’s a reason all the cloud companies settled on VMs over containers. It’s just one line of defence that you otherwise wouldn’t have.
Well, both the Flathub website and KDE Discover list this, so this seems like a GNOME issue and not a Flatpak issue.

KDE Discover:



The Immich app (at least on Android) supports mTLS client certificates, I use that for my instance.
If you really have to use Adobe Acrobat Reader, it works fine in CrossOver, which is paid but it supports the wine developers.
Also if it helps with getting it working in Wine, these are the installers that CrossOver uses:


You need the web site to use a certificate from the same root authority as your client certificate.
I’m not sure if I’ve misunderstood you, but I use Lets Encrypt for the server’s TLS, and then my own CA cert (which is only present on the webserver) for the client’s mTLS and everything works fine, since it’s the client that validates the server’s cert and the server that validates the client’s cert.


Only works with the web UI, no apps support it
Yeah that’s true.
you will get warnings when adding your root certificates to any device
It’s not a root certificate, and I’ve never seen any warnings.
Same, there’s also an unofficial home assistant integration for mine, so I get my brush tracking without ever using the official app.


Possibly mTLS, which you’d configure in your reverse proxy. You could email them the certificate and instructions on installing it. I believe for Chromium browsers on Windows you basically just double click the cert and click through the wizard. Firefox I know has a thing in the settings for importing the cert. Android you just tap on the cert and make sure it opens with ‘Certificate Installer’ if it gives you the option.


There’s some thinner m.2 to PCIe extensions that might work if there’s no space. Then you just use a normal PCIe sata card.


For me, every subnet (except internal only ones) have a global IPv6 prefix, including my Wireguard tunnels. I’ve got a mix of statically assigned and SLAAC. I think I’ve setup DHCPv6 too but it either doesn’t work or nothing uses it.


If anyone’s curious, here’s the leaker’s reasoning: https://www.openwall.com/lists/oss-security/2026/05/07/12
Basically he had no prior knowledge of the vulnerability, he saw the patch go in and wrote a PoC based on that.


Here’s the official docs: https://docs.immich.app/guides/external-library/
They seem to use different paths.
Not to wreck your joke, but certificates have a starting date on them too, so the epoch also won’t work.