I agree with you on the dangers but, as far as being just an
inconvenience, sometimes it only takes a little slow down to have a
big impact on the outcome. Look at the SCUD missiles launched during
Desert Storm. There has been no proof or evidence or claims of
sabotage but, when I was getting out of the military after Desert
Storm, they offered me a position with a cyber-warfare unit to try to
get me to reenlist and they hinted that there might have been "some
reason" that all those SCUD missiles failed or went off target. I
sometimes regret not taking that position because it probably would
have been a very cool job.
On Nov 10, 5:59 am, Lawrence Terrill <
nin...@theterrills.com> wrote:
> I find the suggestion that our military might have intentionally created this code and turned it loose quite disturbing. Malware is much like chemical warfare. At best, you've given your enemy a template to use against the same vulnerabilities that exist in your own infrastructure. At worse, you've screwed up the design, the wind changes, and you've inadvertently attacked yourself.
>
> And in the end, it was never going to 'disable' Iran's ability to manufacture nuclear material. It is at worst a nagging inconvenience that will slow them down a bit. In that sense it seems to mirror the Obama administration in general.
>
> On Nov 9, 2010, at 11:30 AM, Ron Smith wrote:
>
>
>
> > Did the U.S. create software to affect Iran's nuclear capability?
>
> >
http://www.csmonitor.com/USA/2010/0921/Stuxnet-malware-is-weapon-out-...