Hawaiians started their weekend with quite a fright, waking up Saturday morning to a ballistic missile alert that turned out to be a false alarm. In between the public anger, profuse apologies from officials, and geopolitical commentary, it might be hard to find some information for the more technical-minded. For this audience, The Atlantic has compiled a brief history of infrastructure behind emergency alerts.
As a system intended to announce life-critical information when seconds count, all information on the system is prepared ahead of time for immediate delivery. As a large hodgepodge linking together multiple government IT systems, there’s no surprise it is unwieldy to use. These two aspects collided Saturday morning: there was no prepared “Sorry, false alarm” retraction message so one had to be built from scratch using specialized equipment, uploaded across systems, and broadcast 38 minutes after the initial false alarm. In the context of government bureaucracy, that was really fast and must have required hacking through red tape behind the scenes.
However, a single person’s mistake causing such chaos and requiring that much time to correct is unacceptable. This episode has already prompted a lot of questions whose answers will hopefully improve the alert system for everyone’s benefit. At the very least, a retraction is now part of the list of prepared messages. But we’ve also attracted attention of malicious hackers to this system with obvious problems in design, in implementation, and also has access to emergency broadcast channels. The system needs to be fixed before any more chaotic false alarms – either accidental or malicious – erode its credibility.
We’ve covered both the cold-war era CONELRAD and the more recent Emergency Broadcast System. We’ve also seen Dallas’ tornado siren warning system hacked. They weren’t the first, they won’t be the last.
(Image: Test launch of an unarmed Minuteman III ICBM via US Air Force.)
Instructables user [Mike Craghead] was in the middle of building a very compact public computer kiosk when he ran into a problem with the processor fan. It was too big for the enclosure and had to be swapped out with a fan that did not allow the motherboard to monitor its rotational speed.
Motherboards don’t like this situation very much, and each time the computer was started, it would hang at the BIOS screen waiting for someone to press the F1 key to continue. Knowing that everything was just fine, and that there were no BIOS options which would allow him to ignore the error, he crafted a simple solution to the problem.
Since the computer just needed someone to press the F1 key, he figured he could rig up a small dongle that would always hold down the key for him. After verifying that the OS would ignore the stuck key, he tore apart a keyboard and traced the circuit matrix to identify which pins he had to short in order to represent the F1 key press.
Satisfied with his handiwork, he plugged the board into his computer and found that everything worked just fine. Sure it might not be the most elegant solution to the problem, but it gets the job done at a cost of zero dollars – you can’t beat that!
The Acer Aspire One is a netbook that often ships with a Linux OS preinstalled. This is great for fans of open source as market share is calculated based on units shipped, not what users install after they buy the hardware. Unfortunately there is a pretty major flaw that can cause a “failed to initialize HAL” error as seen above. [Michael Crummy] came up with a set of steps you can use to recover from this error.
So what is this error? HAL stands for Hardware Abstraction Layer and it’s what allows one user interface to communicate with many different types of hardware. If you’re the proud owner of an Aspire One and are struck with this error you will suddenly find that you can no longer use the USB ports, card readers, wired or wireless network connectors, or the sound card. So you can’t connect to the Internet, and you can’t get any files on or off of the device using the currently installed operating system. For an OS that [Neal Stephenson] once described as “like the M1 tanks of the U.S. Army, made of space-age materials and jammed with sophisticated technology” this is a very big problem.
We know what you’re thinking… boot into a live session on a thumb drive and get what you need from the hard disk. Well that’s all fine and dandy, but you shouldn’t ever be forced to clean install Linux to fix a problem. So check out [Michael’s] method and make sure you turn off the Acer live update server which was mostly likely the cause of the problem in the first place.
One of the worst moments almost every hacker has experienced is a hard drive inexplicably dieing. And of course, its at the most inopportune time and you’ve had no chance to backup!
Recently there has been an influx of Seagate hard drives (specifically the 2700.11s) kicking the bucket with firmware errors 0LBA and BSY. The good news is [Gradius2] has made guides to unbrick your drive without having to match serials.
The procedure is lengthy, complicated, can easily become expensive, and there is the possibility of losing your data so it’s not recommended if you’re only getting those pictures of Mr.Fluffykins back. In such a case, Thermite might be a bit better solution.