Idk about the details, I just know that Firefox (just like Chrome, afaik) has separate channels for certificate revocations, which is what matters in this case. You could last update the app five years ago or today, you’d still have about the same experience with the eMudhra certs. Which is actually good, since the web relies so much on TLS security.

Firefox updates certificate revocations without requiring an update of the app itself.

/cc @Ohh@lemmy.ml

They’ve been doing that for ages already.

That’s the idea, I believe. A password or at least a gesture passcode remains the most secure option, since it can’t just be taken from one’s hand without some rubber-hose cryptanalysis.

However, as someone who’s stuck my finger into Pixel’s fingerprint scanner by accident multiple times, having thankfully never configured it for anything, I don’t think that wiping the phone in such a case is really a good idea.

Open-source software has been used in cars for ages. Daniel Stenberg, the author of curl, has been receiving emails from people complaining about their cars, because his address was listed in the licensing section of the infotainment system’s ‘about’ screen.

Done long ago.

Fun fact, this is also why Macbooks, at least some models, throttle the CPU if the battery is missing. My old Macbook went from 2.4 GHz to 800 MHz without the battery.

Thanks for your input, I didn’t even know that killing customers would increase companies’ revenue.

Yes, it’s relevant, because DEI inherently limits what the company does, and yet the shareholders voted to keep it. Apparently Apple’s shareholders aren’t bigoted idiots.

if 2028 goes Republican in US they probably won’t even do a logo change that pride month

Nice job showing your ass here, because Apple never ‘changed the logo’ for the pride month. Where the fuck are they supposed to change it, on the Macbooks?

Just to check, would Apple’s commitment to DEI policies look as thrown-away profit to shareholders?

a handful of other names

Closer to three handfuls, as is tradition among edgier edm producers.

Some pseudofiles under /proc are only readable by the user running the process, and of course root can read everything. So it’s the standard Unix security model, afaics.

For example, any process’ command-line arguments are famously visible to everyone, while the environment variables only to the user of the process.

That raises the question of how their ps, top, lsof and such work, since afaik in Linux they read from /proc.

P.S. Looks like BSDs tug at the kernel via syscalls, namely sysctl and also the ‘kvm interface’ in the case of MacOS (not sure what ‘kvm’ thing is meant here). Seems vaguely reasonable, since procfs also queries the kernel for the info, so about the same resources would be used, perhaps even with the overhead of filesystem traversal and string-numbers conversion.

These days there can be a dozen virtual filesystems doing various stuff. If you ever want to get quite baffled, install a terminal emulator on an Android phone (not Termux) and run mount.