Most of the software needed to provide a useful desktop Linux never runs on servers, so we cannot conclude that it is safe to use desktop Linux just because Linux is a popular server OS.
Also, at organizations like Google with a good reputation for security, most of the Linux installs are connected to internal networks that are quite difficult to break into from the open internet. The Linux installs at Google that are connected directly to the open internet are very carefully configured to minimize attack surface.
And Google has an internal team of Linux kernel maintainers that do not share most of their work outside Google.
Not any more. Not with a new LPE being discovered every week. Containers are dead, user accounts are dead, VMs are on shaky ground. We're currently getting the same level of security from Linux that we got from Windows ME.
Aaaand now we have sshhole: you can just log into some machines by typing a password longer than 256 chars. Proving my point. The CADT development model (a.k.a. open source) cannot produce secure software, period.
That's changed a bit in the last few years! I'm in somewhat rural Oregon (The Dalles) and in practice none of our gas stations really do full service anymore. Gas prices didn't go down at all
Most people don't need to care about that. If you're writing something that's gonna be used by a fixed number of real humans a few times (or a even a few 1000) times a day the overhead isn't gonna matter
> What happens to my in-person or virtual registration fee?
> Information regarding GHC registration and other financial matters will be communicated to you promptly once we obtain a clearer understanding of AnitaB.org ’s financial condition.
that might be a nail in the conference's coffin...
You're not wrong for wanting your money back for services not provided, but also recognize this organization is to promote women in tech. A charge back kicks them while they are down.
They have nobody to blame but themselves for that. Charities have a duty to conduct themselves with integrity just as much as anyone else does. This has been a regular event for many years. Normally you would expect there to be contingency plans and as other commentators have posted, for ticket sales to mostly fund next years event not the current one.
Actually, in many cases the opposite. If you have a classical Corner control, it can be used with a part of your palm with less movement, and you finger doesn't contort
"far more natural" would be if you moved pinky up or down. Sideways movements are only natural for your thumb
I've been doing Linux sys-admin work for 10+ years. Used to be I could read the full report on what ever vulnerabilities came out and triage which servers needed to be updated now and which could wait. A few years ago notifications started having so many it would take more time/effort to read everything than it would to patch everything. With this notification there's even ten times more...
>Note, due to the layer at which the Linux kernel is in a system, almost any bug might be exploitable to compromise the security of the kernel, but the possibility of exploitation is often not evident when the bug is fixed. Because of this, the CVE assignment team are overly cautious and assign CVE numbers to any bugfix that they identify. This explains the seemingly large number of CVEs that are issued by the Linux kernel team.
The amount of updates on Debian "stable" has become ridiculous, it's a daily rolling release of backports at this point.
Microsoft kinda got this right by doing it once a month, unless it's something horribly bad, you can plan your maintenance around a predictable calendar.
I kept asking myself "is this ai written" while reading it to. Nothing to do wit h the em dashes. Phrasing like:
> RIP, primary vector index.
> The solution to these problems is simple: don't key on the ANN address. That is precisely the change turbopuffer v3 makes. As you can imagine, it is not a trivial change."
Cute heading, followed by wordy opening sentence that feels like it's repeating stuff even when it's not
reply