US Military Leaks its Secrets Online
athloi writes "Detailed schematics of a military detainee holding facility in southern Iraq, geographical surveys and aerial photographs of two military airfields outside Baghdad and plans for a new fuel farm at Bagram Air Base in Afghanistan are among the items accidentally left online by government agencies and contractors."
see this is what I like, I'm fine with the government invading privacy just as long as they don't get to have any either.
From TFA: The DOD has a special category of Unclassified documents called "For Official Use Only" (FOUO) which prevents the information from being released to the public under the FOIA. This information was not classified, but was not supposed to be released.
Please! So those were the "real" plans, huh? Nod Nod Wink Wink..
What?
And somehow, these people manage to keep secrets about aliens, JFK, weapon programs, etc.? ;)
"The posting of private material on publicly available FTP servers"
$ ftp ftp.usmilitary.com
220 FTP server (SunOS 4.1) ready.
Name (ftp.usmilitary.com): guest
331 Guest login ok, send ident as password.
Password: guest@guest.com
ftp>
Thankfully, they caught on and learned their lesson : "the SRA anonymous ftp server has been shutdown indefinitely. In the coming months, a new secure ftp site will be introduced that will replace the functionality of this site."
$sftp guest@sftp.usmilitary.com
Connecting to sftp.usmilitary.com...
Password: guest@guest.com
sftp>
Gopher... No one looks there!
> the SRA anonymous ftp server has been shutdown indefinitely
Anonymous?... FTP? They may have as well put them on bitorrent and named them britneys_boobies.zip
boycott slashdot February 10th - 17th check out: altSlashdot.org
I work in a class environment. I'll try to answer this.
Why should the OS care? Who is going to build an OS that can determine what is class or not. That is the owner of the datas (data's?) job. The computer does not care. It happily does what it does - manage data. It is not its job to determine what is safe and what is not.
That is for people to determine. In the end it is people who decide what goes where. I like it this way as there is some accountability and a paper (electronic) trail.
So you write an app that determines what is class. Oops! The DB is down/not up to date/hosed by a virus. In other words, you is funked.
Air gap. We have that. Locked ports. We have that. Two man rule. We have that. Can't talk beyond this. Sorry.
My point is technology can only go so far in protecting stuff. The people doing this stuff only need to think of a few words.
VPN. SecureID. One time passwords.
But ftp with no passwords and not even sftp with passwords?
Fire them all.
qz
Privacy Information, Social security numbers, medical, etc.
Company Trade Secrets
Legal documents, law enforcement documents, with limits
And there are others, some discretionary. Full definition in Chapter 4 here (~100 page PDF):
http://www.dtra.mil/documents/be/5400.7-R.pdf BUT, from Chapter 4:
C4.1.1. General. Information that has not been given a security classification pursuant to the criteria of an Executive Order, but which may be withheld from the public because disclosure would cause a foreseeable harm to an interest protected by one or more FOIA Exemptions 2 through 9 (see Chapter C3.) shall be considered as being for official use only (FOUO). No other material shall be considered FOUO and FOUO is not authorized as an anemic form of classification to protect national security interests..
The military accidentally leaks valuable information, and the military intentionally "leaks" disinformation. It is not an either/or thing.
"Leaking" disinformation would be useless if the military didn't actually leak real information. And if you do accidentally leak real information, it only makes sense to also release disinformation to create uncertainty.
But there is probably no way that layman like most of us here can determine if this is fake or real simply from the information in the article.