Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can reflash however you want for some bugs. The deal would be to make it a dormant attack not a destroy all in one go and expose the payload. There have been successful hacks where a buffer overflow was inserted in in a one off write, that was then targeted when needed. If employed carefully in special situations, this could be an important weapon. There are also deeper levels of compromise: why compromise the source code or a the firmware binary when you can permanently compromise the production in a subtle way. Working your penetration slowly so that the whole plant or even production system must be scrapped by the enemy. At the very least gather intel.

Look at successful cyber campaigns like stuxnet or an actual hardware sabotage from Israel. The attacks were dormant until they were ready for maximum effect. Randomly disabling a production site, without a strategic context, is going to be an isolated win, or an operational victory.

I remember reading some articles about the pentagon being a bit upset at some of the strategic decisions of Ukraine's armed forces where they often push for morale boosting moments at big costs(i think 2 years ago they spent lots of resources to get a strategically irrelevant town). And honestly this is also what it looks like: You dont see a coordinated attack but spurious disconnected events. I think when you are gasping for air you hold on to anything you can, but still the goal is to win, not just look like winning.



I still think they'd work it out pretty fast. I'm sure sabotage is pretty high on the list of things the Russians would be thinking about.

It's a good idea, I just think if the goal is to stop the drones working, what better way to do that then to destroy the manufacturing capabilities as often as possible?

Even in the case you describe, you're allowing them to have drones and still do some damage.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: