Winston
Lorenzo von Matterhorn
- Joined
- Jan 31, 2009
- Messages
- 9,559
- Reaction score
- 1,732
New Self-Driving Shuttle in Las Vegas Crashes Just Hours After Launch
Nov 8, 2017
https://www.thedrive.com/news/15914...-in-las-vegas-crashes-just-hours-after-launch
Multiple humans at fault here - the car's programmers (it didn't back up when it OBVIOUSLY should have) and the truck driver. Imagine how many obvious bugs are going to be found in vehicle programming and not so obvious avenues to hacking which will not be found. Also, when the car's choice is to hit two or more pedestrians or cyclists by avoiding an oncoming semi or plow you into the semi, what choice will it make for YOU?
Considering the already insane level of vulnerability of our national infrastructure to hack attacks, what will it be like if our driverless transportation systems are shut down when people's cars begin to run off the road or into each other or semi trucks due to just SUSPECTED hacks? How long can large cities survive without stuff like food and fuel constantly being trucked in?
Self-driving vehicles without the ability for human-controlled MANUAL driving aren't smart at all, IMO, but that's exactly the route being taken.
The outstanding documentary, "Zero Days" reveals amazing leaks from various NSA personnel (combined into one digitally created female) about OUR cyberwarfare capabilities:
[video=youtube;J50bUcf8gfc]https://www.youtube.com/watch?v=J50bUcf8gfc[/video]
Just the comments on Nitro Zeus begin at 1:45:25. WE are more vulnerable to this sort of thing than any of our adversaries which is undoubtedly why this capability is, like nuclear weapons, held in reserve as a last resort. You can just bet that Iran isn't our only target for such malware, some of it apparently already in place. Now, add the potential ability in the not so distant future for adversaries to shut down OUR entire transportation system.
Nitro Zeus
https://en.wikipedia.org/wiki/Nitro_Zeus
Nitro Zeus is a project name for a well funded comprehensive cyber attack plan created as a mitigation strategy after the Stuxnet malware campaign and its aftermath.[1] Unlike Stuxnet, that was loaded onto a system after the design phase to affect its proper operation, Nitro Zeus's objectives are built into a system during the design phase unbeknownst to the system users. This builtin feature allows a more assured and effective cyber attack against the system's users[2].
The information about its existence was raised during research and interviews carried out by Alex Gibney for his Zero Days documentary film. The proposed long term widespread infiltration of major Iranian systems would disrupt and degrade communications, power grid, and other vital systems as desired by the cyber attackers. This was to be achieved by electronic implants in Iranian computer networks. [3] The project was seen as one pathway in alternatives to full-scale war. There was no requirement for this type of plan after the Iran Nuclear Deal was signed.
This is not at all new. Here's what we caused to happen in the USSR 35 years ago:
https://www.damninteresting.com/the-farewell-dossier/
Excerpts:
In 1982, operatives from the USSR’s Committee for State Security—known internationally as the KGB—celebrated the procurement of a very elusive bit of Western technology. The Soviets were developing a highly lucrative pipeline to carry natural gas across the expanse of Siberia, but they lacked the software to manage the complex array of pumps, valves, turbines, and storage facilities that the system would require. The United States possessed such software, but the US government had predictably turned down their Cold War opponent’s request to purchase the product.
Never ones to allow the limitations of the law to dictate their actions, the KGB officials inserted an agent to abduct the technology from a Canadian firm. Unbeknownst to the Soviet spies, the software they stole sported a little something extra: a few lines of computer code which had been inserted just for them.
After the US government denied the USSR’s request to buy the software to automate their new trans-Siberian pipeline, a KGB agent was covertly sent to a Canadian company to steal the software. A new batch of Farewell Dossier documents brought these efforts to the attention of the CIA, prompting US agents to tailor a special version of the software for the Soviets, and plant it at the company in question. Delighted at the ease of procuring the program, the Soviets tested their complete pipeline automation system and everything seemed to hum along smoothly. By about the middle of 1982, the pipeline was pumping massive amounts of natural gas across Kazakhstan and Russia to Eastern Europe, bringing in a tidy profit for the USSR government.
Some weeks after going online, in the summer of 1982, the clandestine code in the pipeline control program asserted itself. Disguised as an automated system test, the software instructed a series of valves, turbines, and pumps to increase the pipeline’s pressure far beyond its capacity, putting considerable strain on the line’s many joints and welds over a period of time. One day, somewhere in the cold loneliness of Siberia, the overexerted pipeline finally succumbed to the pressure.
As satellites for the North American Aerospace Defense Command (NORAD) watched from orbit, a massive explosion rocked the Siberian wilderness. The fireball had an estimated destructive power of three kilotons, or about 1/4 the strength of the Hiroshima bomb. Initially NORAD suspected a nuclear test, but there was only silence from the satellites which would have detected the telltale electromagnetic signature. US military officials who were not privy to the Farewell Dossier activities were understandably concerned about the event—one of the largest non-nuclear blasts ever recorded—but the CIA quietly assured them that there was nothing to worry about. It would be fourteen years before the real cause of the event would be revealed.
Nov 8, 2017
https://www.thedrive.com/news/15914...-in-las-vegas-crashes-just-hours-after-launch
Multiple humans at fault here - the car's programmers (it didn't back up when it OBVIOUSLY should have) and the truck driver. Imagine how many obvious bugs are going to be found in vehicle programming and not so obvious avenues to hacking which will not be found. Also, when the car's choice is to hit two or more pedestrians or cyclists by avoiding an oncoming semi or plow you into the semi, what choice will it make for YOU?
Considering the already insane level of vulnerability of our national infrastructure to hack attacks, what will it be like if our driverless transportation systems are shut down when people's cars begin to run off the road or into each other or semi trucks due to just SUSPECTED hacks? How long can large cities survive without stuff like food and fuel constantly being trucked in?
Self-driving vehicles without the ability for human-controlled MANUAL driving aren't smart at all, IMO, but that's exactly the route being taken.
The outstanding documentary, "Zero Days" reveals amazing leaks from various NSA personnel (combined into one digitally created female) about OUR cyberwarfare capabilities:
[video=youtube;J50bUcf8gfc]https://www.youtube.com/watch?v=J50bUcf8gfc[/video]
Just the comments on Nitro Zeus begin at 1:45:25. WE are more vulnerable to this sort of thing than any of our adversaries which is undoubtedly why this capability is, like nuclear weapons, held in reserve as a last resort. You can just bet that Iran isn't our only target for such malware, some of it apparently already in place. Now, add the potential ability in the not so distant future for adversaries to shut down OUR entire transportation system.
Nitro Zeus
https://en.wikipedia.org/wiki/Nitro_Zeus
Nitro Zeus is a project name for a well funded comprehensive cyber attack plan created as a mitigation strategy after the Stuxnet malware campaign and its aftermath.[1] Unlike Stuxnet, that was loaded onto a system after the design phase to affect its proper operation, Nitro Zeus's objectives are built into a system during the design phase unbeknownst to the system users. This builtin feature allows a more assured and effective cyber attack against the system's users[2].
The information about its existence was raised during research and interviews carried out by Alex Gibney for his Zero Days documentary film. The proposed long term widespread infiltration of major Iranian systems would disrupt and degrade communications, power grid, and other vital systems as desired by the cyber attackers. This was to be achieved by electronic implants in Iranian computer networks. [3] The project was seen as one pathway in alternatives to full-scale war. There was no requirement for this type of plan after the Iran Nuclear Deal was signed.
This is not at all new. Here's what we caused to happen in the USSR 35 years ago:
https://www.damninteresting.com/the-farewell-dossier/
Excerpts:
In 1982, operatives from the USSR’s Committee for State Security—known internationally as the KGB—celebrated the procurement of a very elusive bit of Western technology. The Soviets were developing a highly lucrative pipeline to carry natural gas across the expanse of Siberia, but they lacked the software to manage the complex array of pumps, valves, turbines, and storage facilities that the system would require. The United States possessed such software, but the US government had predictably turned down their Cold War opponent’s request to purchase the product.
Never ones to allow the limitations of the law to dictate their actions, the KGB officials inserted an agent to abduct the technology from a Canadian firm. Unbeknownst to the Soviet spies, the software they stole sported a little something extra: a few lines of computer code which had been inserted just for them.
After the US government denied the USSR’s request to buy the software to automate their new trans-Siberian pipeline, a KGB agent was covertly sent to a Canadian company to steal the software. A new batch of Farewell Dossier documents brought these efforts to the attention of the CIA, prompting US agents to tailor a special version of the software for the Soviets, and plant it at the company in question. Delighted at the ease of procuring the program, the Soviets tested their complete pipeline automation system and everything seemed to hum along smoothly. By about the middle of 1982, the pipeline was pumping massive amounts of natural gas across Kazakhstan and Russia to Eastern Europe, bringing in a tidy profit for the USSR government.
Some weeks after going online, in the summer of 1982, the clandestine code in the pipeline control program asserted itself. Disguised as an automated system test, the software instructed a series of valves, turbines, and pumps to increase the pipeline’s pressure far beyond its capacity, putting considerable strain on the line’s many joints and welds over a period of time. One day, somewhere in the cold loneliness of Siberia, the overexerted pipeline finally succumbed to the pressure.
As satellites for the North American Aerospace Defense Command (NORAD) watched from orbit, a massive explosion rocked the Siberian wilderness. The fireball had an estimated destructive power of three kilotons, or about 1/4 the strength of the Hiroshima bomb. Initially NORAD suspected a nuclear test, but there was only silence from the satellites which would have detected the telltale electromagnetic signature. US military officials who were not privy to the Farewell Dossier activities were understandably concerned about the event—one of the largest non-nuclear blasts ever recorded—but the CIA quietly assured them that there was nothing to worry about. It would be fourteen years before the real cause of the event would be revealed.
