• 3 Posts
  • 98 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle







  • There is so much old and creaky stuff lying around and people have no idea what it does. Beige boxes in a cabinet that when we had to decommission it the only way to understand what it does was doing the scream test: turn it off and see who screams!

    Or even stuff that was deployed as IaC by an engineer but then they left and so was managed “clickOps”, but documentation never updated.

    When people talk about the Tier1 systems they often forget the peripheral stuff required to make them work. Sure the super mega shiny ERP system is clustered, with FT and DR, backups off site etc. But it talks to the rest of the world through an internal smtp server running on a Linux box under the stairs connected to a single consumer grade switch (I’ve seen this. Dust bunnies were almost sentient lol).

    Everyone wants the new shiny stuff but nobody wants to take care of the old stuff.

    Or they say “oh we need a new VM quickly, we’ll install the old way and then migrate to a container in the cloud”. And guess what, it never happens.


  • Im_old@lemmy.worldtoPrivacy@lemmy.mlHow save is XMPP really?
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    It depends on the client and the security implementations they support. For example IIRC no client support the last version of OMEMO (I think it was about OMEMO, I remember an article about it some time ago). Also are you sure that all the other people’s clients are on the same version and you’re not susceptible to a downgrade attack?

    Unless you are ready to/want to control the whole environment (i.e. at least the clients and possibly the server), look into simplex.chat













  • That article is SO wrong. You don’t run one instance of a tier1 application. And they are on separate DCs, on separate networks, and the firewall rules allow only for application traffic. Management (rdp/ssh) is from another network, through bastion servers. At the very least you have daily/monthly/yearly (yes, yearly) backups. And you take snapshots before patching/app upgrades. Or you even move to containers, with bare hypervisors deployed in minutes via netinstall, configured via ansible. You got infected? Too bad, reinstall and redeploy. There will be downtime but not horrible. The DBs/storage are another matter of course, but that’s why you have synchronous and asynchronous replicas, read only replicas, offsites, etc. But for the love of what you have dear, don’t run stuff on bare metal because “what if the hypervisor gets infected”. Consider the attack vector and work around that.