- cross-posted to:
- technews@radiation.party
- cross-posted to:
- technews@radiation.party
An update:
- fmhy.ml is gone, due to the ongoing fiasco with mali government taking all their .ml domains back
- As such, lemmy.fmhy.ml is also gone, we are currently exploring ways to refederate (or somehow restart federation entirely) without breaking anything substantial
- We have backups, so don’t worry about data loss (you can view them on other instances anyway)
Currently, we have fmhy.net and are exploring options to somehow migrate, thank you for your patience.
Perhaps the military should have a system in place to not allow emails to be sent outside of very specific TLDs if it’s that sensitive? And perhaps have an automated contact book, instead of relying on someone typing out the to: address manually to be able to make that mistake in the first place?
Seems like some very basic security measures for something so serious.
This says that they block outgoing mail to .ml domains.
https://domainincite.com/28814-millions-of-domains-to-be-deleted-as-freenom-loses-its-first-tld
For most situations, there is a global address list that members can use. There are instances where emails need to be sent outside of the .mil domain though, such as to other government agencies that use a .gov, or to contractors on commercial domains, as well as to partner nations that will be on their own countries’ domains.
Internally they do block that but the problem are people outside the network sending something to a .mil address and mistyping.
Yeah that’s super easy to integrate. I used to work in cyber security for a bank and even I was only allowed to send to internal domains initially. I had to file for exceptions for contractors and vendors and stuff.