• 0 Posts
  • 17 Comments
Joined 12 days ago
cake
Cake day: November 10th, 2026

help-circle
  • Sorry, that last comment was rushed and just reacting to the philosophy of “let’s just throw another password around it.”

    My real/main point is about root (sudo) access vs “unprivileged” users. In my experience, sudo is like putting up a (thin) glass window on a house, it’s a great way to communicate to gentle-folk that they are not supposed to come in, the door is locked, but they can still look inside (read access), and if they don’t mind making a mess they can certainly smash the window to bypass the lock, or if the window is too strong for them to break they can more easily burn the whole house down. A sudo locked door might make it necessary to have unusual lock picking skills if you’re going to sneak in, rearrange the furniture, then leave without everyone knowing that things have been messed with on first glance, but it’s not going to stop a DDOS from succeeding. The typical “non-privileged” user with command line access can easily trash most systems into a non-functional state, shortly after exporting most data of any value.

    Then (different, but related rant): all of the “physical access to the device required” attack hardenings are of little help preventing these kind of attacks: https://www.infosecinstitute.com/resources/general-security/usb-killer-how-to-protect-your-devices/

    Systems need good physical security first, and then they need serious least-privilege protection against ALL users, not just those who can get root access. Access to a general purpose terminal, even without root privilege, is more privilege than any untrusted user should ever have.









  • 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.









  • 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.