Yeah, it’s pretty trivial to do, and it’s honestly surprising it took YT so long to do it.

It’s not at all uncommon for fines to be built into an SLA

The organizations they were talking about and I was referring to have a global presence

Plus, it’s not significantly more expensive to have a cold standby in a different geographic location in AWS.

So does an outage, but I get that the C-suite can only think one quarter at a time

It’s also silly for the orgs to not have geographic redundancy.

Yeah, if you’re a major business and don’t have geographic redundancy for your service, you need to rework your BCDR plan.

Thank you for this. I’ve been struggling to get wireguard running in hotio containers on my Synology, and this looks like it might be what I need.

Edit: it worked! Had to fiddle around with it because it didn’t like multiple containers in one compose yaml

Because best practices for connecting an unsupported operating system to the Internet are to not do it.

Even if the OS is safe on the day support ends, a critical vulnerability might be found just a few days later. It’s also possible that an exploit has already been found that the bad actor is sitting on it until support ends.

Even if that doesn’t happen, software developers are going to drop support for the OS and vulnerabilities found in those applications could be used to gain ingress.

No amount of “being careful using the Internet” is going to prevent hacking if the system has exploits. If you context a fresh install of XP to the Internet, your system will be compromised in a matter of minutes.

All of mine are sequestered to their own vlan that can only talk to Home Assistant. But they do have ones that use matter now.

Not immediately, no, but saying you can safely continue using it if you follow Internet use best practices is flat out wrong.

Don’t give out infosec advice if you have no fucking clue what you’re talking about.

That’s about the only reason I’m still sticking with TP-LINK for switches.