I do recommend Gentoo (haven’t tried Funtoo) for the academically inclined. It’s a beast to maintain, but you’ll soon find yourself at ease with configuring and compiling your own kernel, configuring your packages and even making some yourself.
It isn’t as hard as people make it out to be - if you gradually push your boundaries. In particular, it’s good if you already use Arch.
Nobody ever learned from the solarwinds attack. If a massive amount of your infrastructure is backed by some obscure software, bad actors will either try to insert a backdoor or find a zero-day exploit. If people are going to neglect what just happened, crowdstrike will fall heals up, faster than solarwinds did.
I don’t think that rust would have prevented this one, since this isn’t a compile time error (for the code loader).The address dereferencing would have been inside an unsafe block. What was missing was a validity check of the CI build artifacts and payload check on the client side.
I do however, think that the ‘fingers-crossed’ approach to memory safety in C and C++ must stop. Rust is a great fit for this use case.
Why are sensitive or critical hospital systems loaded with bossware? That itself is a breach of medical safety regulations and medical privacy. If such bossware fails for whatever reason - even sabotage, it’s on the leach class. Prosecute them for murder.
Crowdstrike exists for Linux too. In fact, it apparently crashed RHEL and Debian a few months back. That didn’t get so much attention.
Falcon seems to be a cross between an antivirus and an intrusion detection system (IDS). There are many antiviruses on Linux, but only one FOSS AV is popular - ClamAV. As for IDS, snort is an example.
But in the true sense, Falcon is much more than just an AV and IDS. It’s a way to detect breaches and report it back to CrowdStrike’s threat detection and analysis teams. I don’t think there exists a proper alternative even in the commercial sector.
In that case, it’s time for the average workers to sabotage the bossware. Let the leech class solve the problem they create.
Google has discovered that FOSS software under their full control is better than pure proprietary software for monopoly abuse and rent seeking. With FOSS software, they enjoy the automatic popularity that they otherwise would have had to market very hard for. At the same time, none of Google’s free software is truly free. Google devs regularly neglect and reject overwhelming user requirements (jpegxl in chrome is probably the best example of this) and choose designs that clearly favor the company monetarily. It isn’t even practical for normal people to fork their projects.
Google often uses their ‘FOSS’ projects to twist open standards or the market to their advantage. Android and Chrome are very significant players in this regard. Using Chrome, Google even managed to make the W3C standard too complicated for others to make alternative browsers easily. Google has similar ambitions in the multimedia market. They want to replace the monopolistic media formats with quasi-monopolistic formats like webp and av1 instead of truly open ones like jpegxl.
It’s still possible on almost any distro with pyenv or asdf-vm.
Nice idea!
In addition, we could have an allowlist for honest bots (like search crawlers).
I wish there was something more interesting to do there.
You are not expected to remember a v6 address - or even v4 for that matter. They are designed for machines. DNS is designed for humans.
What do you do on the yggdrasil network?
We need three four things:
Oh! I misunderstood. Sorry! Glad to meet a fellow Gentoo here!
I use Gentoo with OpenRC. So my position in this matter should be clear. Anyway, check the last paragraph again to see what I think about systemd’s modularity.
Python decided to use a single convention (semantic whitespace) instead of two separate ones for machine decodeable scoping and manual/visual scoping. That’s part of Python’s design principle. The program should behave exactly like what people expect it to (without strenuous reasoning exercises).
But some people treat it as the original sin. Not surprised though. I’ve seen developers and engineers nurture weird irrational hatred towards all sorts of conventions. It’s like a phobia.
Similar views about yaml. It may not be the most elegant - it had to be the superset of JSON, after all. But Yaml is a semi-configuration language while JSON is a pure serialization language. Try writing a kubernetes manifest or a compose file in pure JSON without whitespace alignment or comments (which pure JSON doesn’t support anyway). Let’s see how pleasant you find it.
The kernel isn’t a place to play politics. You can’t just yank a component out like that on short notice, even if it has such a horrible story attached to it.
Back then, ReiserFS was mildly popular and its use would have been widespread (that includes me). The users of ReiserFS and probably even the other kernel devs had no idea that Hans Reiser was capable of such a crime. Infact, he was known as a computer prodigy back then.
There are plenty of users who don’t have the luxury of migrating data on a short notice to a different filesystem. Disabling the filesystem would have left them high and dry. That’s why the devs gave it a long deprecation period.
The licenses alone are enough to ensure that the opposite happens.
The OP can make the same argument after replacing sudo with doas or su.
I wonder what happened to Tails - the one that started it all.