• 2 Posts
  • 1.46K Comments
Joined 1 year ago
cake
Cake day: September 21st, 2024

help-circle

  • I wouldn’t go onto a teen community and spout off how to make explosives even though they’re relatively safe to a trained individual.

    same reason behind not allowing a hobbyist and amateur community to think that iptables and firewalld is the best/only solution.

    it’s dangerous and someone will get hurt eventually.







  • GreenKnight23@lemmy.worldtoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    15 hours ago
    • anyone gaining physical or remote access to the device can set rules. by protecting the entire network with a hardware firewall you mitigate attack vectors from other hardware on your network that become compromised.
    • iptables and firewalld are notorious for locking users out of the system by overzealous or green system admins. in the msp world this happens practically by the hour.
    • iptables and firewalld can be used against you in the event of a breach. one of the first things an attacker may attempt is to forward ports and lock system admins out as they take over the system.
    • make sure you save your rules properly or they’ll be gone after a reboot or botched upgrade
    • migrating your rules from one system to another when you’re changing hardware or restoring a system is a huge pain in the ass.
    • got a network change that’s going to modify the subnet your systems are on? get ready to migrate all 15 of your devices one by one for the next 8-15 hours (depending on the complexity of your rules)

    it’s far easier, and safer to have all your network config done in the network. from system migrations to securing/hardening. it’s far more efficient and effective to have a single source of truth that manages network routing and firewall rules. hell, you can even have a redundant or load balanced firewall configuration if you’re afraid of a single point of failure.

    point is, firewalld and iptables is for amateur hour and hobbyists.

    if you want to complain that “docker doesn’t respect system firewalls” then at least have the chutzpah enough to do it the right way from the beginning.


  • it’s hilariously depressing how most people hate on Ruby because of the shit Rails does.

    also, Sheon Han(the author), is a corpo-shilling hack that writes predominantly fluff pieces for his silicon valley friends and neighbors.

    don’t believe what he writes because he only gets paid when his opinions garner traffic.

    want to know why Ruby still has a following? same reason why Java is still holding on. Same reason why COBOL and FORTRAN is still going. because it works and people still use it.




  • GreenKnight23@lemmy.worldtoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    7
    ·
    21 hours ago

    What if you rent a bare metal server in a data center?

    any msp will work with your security requirements for a cost. if you can’t afford it, then you shouldn’t be using a msp.

    Or rent a VPS from a basic provider that expects you to do your own firewalling?

    find a better msp. if a vendor you’re paying tells you to fuck off with your requirements for a secure system, they are telling you that you don’t matter to them and their only goal is to take your money.

    Or run your home lab docker host on the same vlan as other less trusted hosts?

    don’t? IDK what to tell you if you understand what a vlan is and still refuse to set one up properly to segment your network securely.

    It would be nice if there was a reliable way to run a firewall on the same host that’s running docker.

    don’t confuse reliable with convenient. iptables and firewalld are not reliable, but they are certainly convenient.

    You may say these are obscure use cases and that they are Wrong and Bad. Maybe you’re right, but personally I think it’s an unfortunate gap in expected functionality, if for no other reason than defense-in-depth.

    poor network architecture is no excuse. do it the proper way or you’re going to get your shit exposed one day.


  • GreenKnight23@lemmy.worldtoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    13
    ·
    23 hours ago

    this is the second time I’ve seen a post like this.

    docker has always been like this. if it’s news to you then you must be new to docker.

    if you’re using the built in firewall to secure your system on your wan, you’re doing it wrong. get a physical firewall. if you’re doing it to secure your lan then you just need to put in some proper routes and let your hardware firewall sort it out with some vlans.

    don’t rely on firewalld or iptables for anything.


  • upvote things I enjoy or agree with.

    I downvote things hate or disagree with.

    one exception though. if what they said is correct or justified, even though I disagree or hate it, I’ll do neither.

    for example, if a comment said “all men are pigs”, I wouldn’t do anything. technically wrong but also not wrong.

    if a comment said, “all men are pigs and deserve to die.” it would get a downvote, unjustified violence against a group is unreasonable and illogical.

    if the comment said, “my husband is a pig. he squeals every time I peg his ass.” that would get an upvote, because it’s hilarious.