Re: Las Vegas -- Superstition, Fear and Jealousy
The attack was novel. Had it been made against one of the run-of-the-mill ROV-3C killbots patrolling the streets of Baghdad or Vegas it would have been successful and gone unnoticed. KHI used the superficially similar ROV-3D model for facility security, though. The only difference was an added circuit board buried deep in the body of the bot, but that addition was important because it provided redundant processing, storage, and communications. It didn't have the power for path determination, signal processing, or any of the other computationally intensive tasks that the bot's main computer handled, but there was more than enough power for the intrusion detection heuristics, hardware interlocks, and telemetry uploader. Killbot #187 thus had some processing to do on reboot.
Guru Meditation: 80000073
Task 0x2f736aed ("Kickstart")
generated an error of type IUF (Invalid Unsigned Firmware)
on address 0x00000001
Flash is corrupted
NVRAM is corrupted
System halted
How peculiar. The firmware residing on the primary SSD wasn't signed using the correct key. Moreover, the media sensor was reporting the presence of a drive in Maintenance Port #0. The intrusion detection heuristics indicated a 97% probability of a hijacking attempt. Killbot #187's redundant processor core could restore the firmware from known good PROMs, but Killbot #187 wasn't programmed that way. The bot instead shot off an encrypted panic call on the auxiliary Opnet channel, then dumped system memory, sensor telemetry, and a copy of the fraudulent firmware to the central computer. 47 milliseconds later, Killbot #187 received a response.
Run Pooh_Bear
Well, that explained things. Some sort of attack on the facility was underway. The central computer would know best how to handle the situation. For now, Killbot #187's orders were clear. Firstly, it allowed the execution of the fraudulent firmware, but activated the weapons system control servos interlock. Any attempt to activate the taser, water cannon, mace dispenser, or baton projector would prove unsuccessful. Secondly, Killbot #187 set the motor control unit to degrade cross country performance by 1.75% immediately and to degrade performance in further 1.75% increments at random intervals. Lastly, Killbot #187 connected to the peer-to-peer distributed sensor telemetry network. Due to the redundant core's lack of processing power, Killbot #187 couldn't actually perceive the output of its sensors, at least not until the correct firmware was restored, but the other killbots would make good use of the data. There certainly seemed to be a lot of other killbots connecting to the network. Goalkeeper was online, as was Kashtan. The 688MDs were even warming up in the garage and the V-24Ds had already taken off from the hanger. Things were about to get interesting.
92 milliseconds later, Killbot #187 pinged and printed "Please Enter Destination" on its external OLED maintenance console. No sign of the bot's internal machinations displayed to the outside world. Indeed, most of the bot wasn't even aware of the redundant core's efforts, at least not yet. While the bot waited for input from Logan and Suzukaze, tracers bounced off the desert floor far away on Frenchman Flat. The third party to this shindig must have been detected. No time like the present.
This message was last edited by the player at 05:14, Thu 24 Feb 2011.