The World's Most Dangerous Password
NonNullSet writes "Minutemen ICBMs were deployed in the early 1960s, and grew to over 1000 in number. They were allegedly protected from a "rogue launch" by an approach known as PAL (Permissive Action Link). The PAL required that the correct 8-digit launch code be entered by the missiliers before the missile would establish ignition. What if all the PAL codes had been set to '00000000,' and 'everyone' in the Strategic Air Command knew it? That is unbelievably what happened, as described in this article from the Center for Defense Information. Not exactly a great example for getting people to choose difficult passwords!"
Now I realize that the movie wasn't nearly as stupid as reality.
[100% ISO 646 Compliant]
SVM, ERGO MONSTRO.
Damn, beat me to it. Here it is anyway since you left out Skroob's quote :)
I remember when legal used to mean lawful, now it means some kind of loophole. - Leo Kessler
i believe it was 111-1111111. the sum of the digits of the second area had to equal 7.
so 111-1111111 aswell as 111-2020201 would work. the first 3 numbers could be anything.
this was on a lot of pre-98 microsoft cds.
more info on microsoft cd-keys
It was Edgar Allan Poe, The Purloined Letter
And damn good it is too.
The best is the enemy of the good
The physical security refers to someone trying to get in from the outside. The two guys inside the silo launch center would be able to get the launch off in time.
Insofar as a single deranged person trying to launch the missiles, both launch keys have to be turned at the same time. The keylocks are separated by a distance making it impossible for a single human being to turn both simultaneously.
Crews are rotated such that the same two are not on duty on any but one shift (to prevent conspiracy), and the crewmen are subjected to some excruciatingly serious background and psychological tests before, during, and after their tours of duty in the silos.
Great care was taken in designing a fail-safe mechanism, where if the protection mechanism fails, it fails into a safe mode (like a default-deny in IPTables).
It was determined that it was better that a few missiles not leave the silos during a nuclear exchange than a few leave a silo during peace-time.
I have something in common with Stephen Hawking...
So assuming the article's correct: a) there wasn't even one password in the launch process at the time, only physical keys, b) four people in the right place could launch nuclear missiles, and no countermeasures would have been able to stop them, and c) given the lack of stringent security in allowing visitors access to those sites, it's not inconceivable that outsiders could have seized the opportunity to take control of two launch centers.
Um, Saddam *DID* allow inspectors! In 2002 and 2003! Bush invaded anyway! (look it up)
I beg to differ. Having formerly done security system installations, this is a quite common practice, especially if you're dealing with security gueards. A large casino I worked for used '2222' for its security codes. McCarren Airport (Las Vegas) prior to 9/11 had '1234' for its password to get into "secure" areas.
It has to be something the lowest common denominator on the security team can remember.
What?? You thinking putting a bar on someone's shoulder makes them "tough?" And just because you call someone a "grunt" they're more suceptible to "blackmail or greed?" Newsflash -- EVERYBODY is suceptible to blackmail and greed. That's why the people who work with nukes are vetted by the security services -- officers and enlisted alike. You think the techs who worked on those missiles didn't know how to bypass those PALs regardless of what password was used?
My point is simple -- don't question someone's patriotism because I'm enlisted -- just because they don't get paid as much doesn't mean their values aren't just as strong as an officer's. The enlisted men and women in the military are the ones you have to trust -- we're the ones who make it all work.
I do not read or respond to AC's. If you want a discussion, log in. Otherwise, don't waste your time.
Gee, you KNOW alot.
Having worked in this field I'll tell you:
1. A civilian is never allowed in a live LCC.
2. The crew is sealed in the live LCC's.
3. To get access to a live LCC is much more then cutting the chain link.
4. Even if you got into one, you need to get into two to do anything.
5. Nevermind the hoards of SP's and armed Helicopters descending around you.
6. While crew members can send messages between LCCs (and I believe between bases, I can't recall) these messages are not and can not be EAM's which are only sendable from the NCA via special terminals.
7. Even if you could send the EAM, who would believe an order coming from the wrong originator.
8. The comm systems in question are not as stupid as e-mail, they are part of a dedicated MLS (b3) system.
9. Nuclear command and control has always relied on personal responsibility, do you think nuclear submarine commanders or the alert bomber force can/could not just decide to launch, or are you deluded enough to think they have some crm114 gizmo that overrides them?
In my place of business I'd have no problem with a null password if all access to the server required two trusted administrators with keys that are kept stored in seperate combination locked safes. In fact, a password beyond the assertion of two trusted people would be stupid, and if you don't trust the people allowing them access to the keys would also be stupid.
Your scenario would be something like this:
1. Something needs done to the server, so you call the CIO
2. He gives you and your other Sys Admin a one-time password for the server.
3. You two go open your safes with your combos (each of you only know one of these combos)
4. You remove your keys and open the server locks.
5. You enter the password you got from the CIO
6. You do your business, and relock the server
7. You put your keys away
Damn, I'd hate to work in your shop. Most of us only have trusted sys admins and single passwords.
Dan
While we're on the subject, and before this gets out of hand, just a reminder to everyone about
The Default Password List
Indispensible tool.
Your Mom
There is someone in the loop. The missle silo's in Colorado are manned by Air Force officers. A college buddy of mine was Air Force ROTC (Reserve Officer Training Corps, pronounced rot-see). In return for the Air Force paying most of his tuition, he serves 4 years active duty and an additional period of time in the reserves. He has been assigned to the "Space and Missiles" program, which means that after a year of training he'll either be sent to "Space" which is mainly research and development, or to "Missiles", which is sitting in the missile silos. Of the people assigned to this program, about 20% go to space, and 80% go to missiles. As my friend describes it, he'd work on a 3 day rotation, where every third day he'd have a 24hr shift in an underground bunker where his primary job would be to wait for the signal to come in and then do the thing with the two keys and entering the final launch code or however it works these days. So there are still people in the loop for the US's long range missiles.
Well, according to Dr Hans Blix (the head of the inspection commission) Iraq was cooperating fairly well. The message that cooperation was inadequate was coming from the same source that was claiming incontrovertible evidence of ongoing WMD activity. Most of the world wanted inspections to continue, based on the doubts raised by the US, in spite of the fact that inspections were revealing nothing.