Lol oh I never said it's a good solution. The worst part isn't running IIS, it's running IIS on a domain controller. The better option is using a different domain for AD than your web domain, as long as it's a publicly registered domain for certificate purposes.
Hilariously, I bet it's because their Active Directory domain is the same as their public domain, and it becomes a massive pain in the ass to hostname the root domain. Yes, externally you can do it just fine, but then it's not consistent internally on their private network.
One solution is you run IIS (or any other web server) purely as a permanent redirect for the internal host, but it would then need to run on each domain controller which brings its own set of issues.
Funnily enough I was in the path of totality at home and my eyes burnt afterwards despite going everything right. Was very confused. Took me a while to realize my eyes burnt from my dumbass neighbors having a bonfire and were burning leaves. I only realized later while grilling when the smoke from that got in my face and gave me the same sensation. Lol. Eyes are fine, just had some temporary irritation at exactly the worst time for my anxiety.
I can from personal experience that there is a huge push to get much more secure in the local government space in the US, including adhering to NIST 800-53, and be audited on it. It's not foolproof, but it's a much needed step forward towards preventing big events becoming breaches. But if they are a breach they'll be lower impact. It's painful to get there, but I've been involved heavily in the conversion in policies and procedures to get there.
I wouldn't say that Windows is malware itself, but rather it wasn't created with a security-first stance, which we absolutely need for all OSes going forward. I say this as someone who ditched Windows as my DD ("I use Arch, btw"). I left Windows more for their policies and subscription models that are becoming increasingly anti-consumer.
With that said, let's not pretend that Linux is immune as has been proven in the past week with xz and liblzma being compromised. Yes, it took 3 years to get to the point their long game paid off, but it still happened through a series of credibility social engineering steps by a single person. (Yes I know others were also trying to do exactly this, but only Jia Tan was successful)
Can confirm that acme.sh is a great option. Way better support of many DNS APIs than Certbot, including easier setup of wildcard certificates. Personally moved to this when Certbot's ability to do RFC2136 (dynamic DNS method that many DNS servers support) was seriously lacking, and never looked back.
I never got far at all in 16, but not because I didn't enjoy it. I just got stuck in a rut last summer and stopped gaming entirely for a couple months and just didn't pick it up again. Maybe when I finish Rebirth in another 100 hours I'll jump back to that lol.
6 though? Have loved that one for a very long time though I may have taken longer to finish it than most anyone ever. Way back when it released as FF3 on SNES, a friend bought it and played for a short while but let me borrow it. I played the hell out of it and had something like 80 hours into it (not sure if I just sucked or idled a lot, don't ask haha). I had made it to right before the final dungeon. But then my friend wanted it back and I said sure, with the intent of finishing it at his house the next time I spent the weekend there gaming, which was common.
Right after I gave it back, his cousin wanted to give it a try and the very first thing he did was delete my save. I watched him do it and just had no words. He didn't realize I hadn't finished and wasn't trying to be an ass, but it just crushed me.
I never went back to play it again until the 2015 release on Steam. Played it on probably 2016. So a minimum 21 years, maybe 22. Lol
Lol I mean it's literally just having a new addition to it and while many will say it's being killed, the amount of content they have added so far in Rebirth has been insane. I have friends who will probably hate it, but it's absolutely beautiful to me and a surprise at every step.
Lol oh I never said it's a good solution. The worst part isn't running IIS, it's running IIS on a domain controller. The better option is using a different domain for AD than your web domain, as long as it's a publicly registered domain for certificate purposes.