11–20 of 100 posts
Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
What do you mean? This is an expected outcome of the "ship ASAP", "competition uber alles" culture, rewarding short term gains over everything else. Our whole technological ecosystem was built on this mindset.
Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
> How else do you explain how woefully unprepared we are? What do you mean? This is an expected outcome of the "ship ASAP", "competition uber alles" culture, rewarding short term gains over everything else. Our whole technological ecosystem was built on this mindset.
Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
Earlier quoted context omitted.
This too is not immune. I get it here too.
Well, the HTML contains some very shady (encoded and obfuscated) JavaScript code. If you want to investigate further replace the "return r;" in the very end of those two "evals" with "console.log(r);" then get the decoded code from the browser's console. Then run through code beautifier (built-in in Firefox JS debugger) to get readable code. But there are more code obfuscations later, though easy to reverse but I don…
Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
Tragedy of the commons. No individual manufacturer really cares about the issues created by the ecosystem of IoT, so they have no real incentive to address it.
The solution of course is alternate economic structures that respect the commons. The distinguished economist Elinor Ostrom wrote a whole book called Governing the Commons which presents real-life alternatives to markets for commons-like economic activity.
Or we could continue marching to the drum of neoliberalism and try to contort markets until they meet our needs. Love me some procrustean capitalism.
Earlier quoted context omitted.
It's a little hard to distinguish worthwhile warnings from the near-constant din of finger-wagging
How... what's the sound of a finger wagging?
global AES-CCM key that Philips uses to encrypt and authenticate new firmware
(I can already imagine how the idiots fixed this: by drawing another set of bytes for a new "authentication" key..)
Earlier quoted context omitted.
It's a little hard to distinguish worthwhile warnings from the near-constant din of finger-wagging
Exactly, for as many legitimate problems I see posted I usually see double as mean fear-mongering stories.
When attacks can be trivially copied, even obscure security issues can become easily exploitable problems under attack from bulk exploitation tools.