UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
1–10 of 13 posts
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#2> emails containing classified information
It's incredibly embarrassing if they're not using any kind of encryption for this.
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#3Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#4Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
It's been this way for 40 years. Are you a taxpayer? I'd rather not pay for any such retrofit. Furthermore, what makes you think that typos won't be made with any different domain name? Why would a fake hypothetical improvement of the situation drive a massive rewrite of millions of lines of code, server configurations, TLS certificates, specification documents...?
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#5Why is classified info allowed on an internet connected computer in the first place?
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#6Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
The USA gets those top level TLDs because that's who created the Internet in the first place. It's an outgrowth of a US military project called ARPANET.
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#7Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
This was discussed just a few days ago: https://news.ycombinator.com/item?id=36836843
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#8Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
It's been this way for 40 years. Are you a taxpayer? I'd rather not pay for any such retrofit. Furthermore, what makes you think that typos won't be made with any different domain name? Why would a fake hypothetical improvement of the situation drive a massive rewrite of millions of lines of code, server configurations, TLS certificates, specification documents...?
I'm pretty sure the GP's point was that the US shouldn't have .gov/.mil etc, every country essentially has a form of government and military — And besides .gov.us would be more explicit.
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#9Earlier quoted context omitted.
It's been this way for 40 years. Are you a taxpayer? I'd rather not pay for any such retrofit. Furthermore, what makes you think that typos won't be made with any different domain name? Why would a fake hypothetical improvement of the situation drive a massive rewrite of millions of lines of code, server configurations, TLS certificates, specification documents...?
I'm pretty sure the GP's point was that the US shouldn't have .gov/.mil etc, every country essentially has a form of government and military — And besides .gov.us would be more explicit.
Inventors' privilege.
Re: UK MoD accidentally sends classified emails meant for US (.mil) to Mali (.ml)
#10Well maybe the USA shouldn't get those top level TLDs? (Eg .gov or .mil or .edu). What's wrong with them having to use a second level domain like ".us.gov"?
It's been this way for 40 years. Are you a taxpayer? I'd rather not pay for any such retrofit. Furthermore, what makes you think that typos won't be made with any different domain name? Why would a fake hypothetical improvement of the situation drive a massive rewrite of millions of lines of code, server configurations, TLS certificates, specification documents...?
You're vastly exaggerating the costs of changing domains (and setting up a redirect).
I'm glad you mention TLS certificate, because those are an ongoing thing, not something you set up once leave unchanged for 40 years.