

I like write filters -> mostly immutable systems. SHTF? reboot ASAP.


I like write filters -> mostly immutable systems. SHTF? reboot ASAP.


Most shell users have enough privilege to read (exfiltrate) most data-value from a server, and they almost always have the capacity to damage it beyond functional operation.


It’s nice that your system has layers, but when the cutworms get on your onion they can still spoil the whole thing.


if an hostile actor gets a shell on your server, you are fucked anyway.
I keep telling EVERYONE this, and we continue to get “findings” around privilege escalation.


I’m going to take exception right here:
“Install Essential Administrative Tools”
The first thing you do to lock down a server is: Uninstall everything that is non-essential.
Do you need any wireless access to the server? If not, remove all WiFi, Bluetooth, and other wireless support from the kernel (block the modules).
Do you need anyone to be able to plug in a USB dongle that can bridge to ethernet? Or anything else?
Remove support for everything you don’t need first, un-necessary attack surface is the first foot-gun.
Are these administrative tools all essential? Keep / install what you need, sudo apt purge the rest.
Do you know WTF you’re doing with Docker containers and firewalls / iptables? The thing to do is learn how that really works, before getting your application servers / containers up on the open internet.
Do you know what un-necessary attack surfaces exist within your container images? That’s another step toward a hardened system - know what you’re running, know what that means, and
above all else: run as little as possible.
It’s frankly incredible that his shallow writing became a cultural icon in the west.
Accessible, relatable, not too challenging for a lot of people to imagine.


is iOS macOS now?


Microsoft is bad enough that I know a few governments which have switched over.


Outsourcing.


The Linux Foundation receives approximately $133 million annually in membership dues and donations from its corporate and organizational members.
I don’t know who is arguing this because it’s incredibly stupid.
It’s not a hard question to solve: who profits from the argument?
Almost all modern architecture would collapse without the open source ecosystem.
If you yanked it away all at once, sure. Just like society would collapse if we quit delivering gasoline and diesel to the filling stations, or electricity to the grid.
If the opensource ecosystem “went closed” today, meaning: no new developments or changes allowed to be used by commercial entities, there would be an initial surge-panic to bring maintenance of the open source tools they use in-house, probably under shared development agreements - it would be interesting to see how the corporations handle that hypothetical scenario, but I don’t think they’d collapse at any greater rate than they already collapse as part of the course of regular business.
The ironic thing I think would come out of the open source community “cutting off” business use of their newly developed things is: I would predict business to adopt the open model to keep their customers off their backs, not have to handle support the way they did in the 1980s/ early 90s - that was super expensive as compared to: here’s a link to our website, you can find what you’re asking for in there.
sudo is a great tool, for people who play nicely.
It’s like a lock on a glass door, with a rock garden outside.