News for hackers. Stuff that matters.
Re:Writing a firmware-only keylogger by matheusmoreira on Monday July 05, 2021 @03:43PM (#27741216)
Just make companies liable for any damage caused by their crappy products. Make them pay billions in damages every time somebody gets hacked because of their negligence. Then they'll start caring about the quality of their software instead of treating it as a cost center.
Re:Writing a firmware-only keylogger by joe_the_user on Monday July 05, 2021 @04:53PM (#27741714)
The implication that software providers should be liable seems to reappear eternally here and remains misguided. Even when we're essentially discussing hardware here.

Software is the perhaps that area where "good" or "crappy" is most undetermined. A given piece of software can be bullet-proof today and a catastrophic hole can appear tomorrow. And even if the producer releases an update, there's no guarantee it will be picked-up.

Overall situation is that what's needed is standards of software use for those companies which actually do damage. Without standards, your use of "crappy" is meaningless.

Re:Writing a firmware-only keylogger by matheusmoreira on Monday July 05, 2021 @06:00PM (#27742210)
> A given piece of software can be bullet-proof today and a catastrophic hole can appear tomorrow.

Sometimes you do everything you can and things still go wrong. That's okay.

What happens in practice is totally different though. Gross negligence is endemic in the technology industry. Most companies out there simply don't give a shit. Their negligence is deliberate, calculated and pre-meditated. They know exactly how much damage they're causing and they don't care because caring costs money.

> Without standards, your use of "crappy" is meaningless.

It's not meaningless at all. For example, nearly every laptop manufacturer I've ever seen has delivered to me software that is unambiguously bad. This opinion is not controversial at all. You just need to fire up some manufacturer app to see just how incredibly bad they are.

I've posted about that here many times and people explained to me that the software is garbage because hardware companies literally don't care about it. They see it as just additional costs to be eliminated and as a result we get products which are total crap. My laptop came with a driver that intercepts my keystrokes and sends signals to the keyboard so that it can light up the LEDs under the keys I pressed. What caused an insane design like this to even come into existence is beyond me, no doubt it came down to saving a few cents in manufacturing. I replaced this functionality with free software and I'm not sure if I even want to know whether there are any vulnerabilities in that driver.

Re:Writing a firmware-only keylogger by brokenmachine on Friday July 09, 2021 @01:12AM (#27780657)
>My laptop came with a driver that intercepts my keystrokes and sends signals to the keyboard so that it can light up the LEDs under the keys I pressed. What caused an insane design like this to even come into existence is beyond me, no doubt it came down to saving a few cents in manufacturing. I replaced this functionality with free software and I'm not sure if I even want to know whether there are any vulnerabilities in that driver.

That sounds pretty cool and hackable actually.

Re:Writing a firmware-only keylogger by gnopgnip on Monday July 05, 2021 @05:15PM (#27741874)
This is how malpractice qorks in every other injury. It isn't just about damage being caused by the software, but if there was a violation of the reasonble standard of care
Re:Writing a firmware-only keylogger by Quekid5 on Monday July 05, 2021 @06:14PM (#27742302)
Exactly. Us engineering types tend to underestimate how much intent and judgment matters when it comes to matters of malpractice (and similar) laws.
Re:Writing a firmware-only keylogger by sellyme on Monday July 05, 2021 @08:58PM (#27743292)
> A given piece of software can be bullet-proof today and a catastrophic hole can appear tomorrow.

Only because you didn't notice the catastrophic hole today, and that's true of everything. When a building collapses the construction company/architects can't really get out of that by going "well it was perfectly fine yesterday, it's hardly our fault!", I don't see why we'd accept that attitude from software engineers.

Re:Writing a firmware-only keylogger by nitrogen on Monday July 05, 2021 @09:14PM (#27743357)
The state space of a complex piece of software is vastly larger than that of a building, and the desirable states within that space are not continuous, while a building's desirable state space is pretty smooth. It's like the difference between walking along the knife edge of a fractal vs. standing on top of a mostly smooth hill.

Because of that, software simply can't be treated the same as other engineering disciplines, at least not yet.

Re:Writing a firmware-only keylogger by Nextgrid on Monday July 05, 2021 @09:35PM (#27743428)
> The state space of a complex piece of software is vastly larger than that of a building

Is it? Unless we can accurately simulate reality at the atom level and bruteforce building designs against every possible scenario to make sure it doesn't fail catastrophically, it's still all down to prior knowledge/experience, reasonable assumptions, approximations and measurements, just like in software. If anything, software is easier, as with enough efforts (formal methods, etc) you can get to prove the correctness of your software, but you can't really do so with a building.

A large chunk of software vulnerabilities is either due to outright incompetence, legitimate mistakes or cost-cutting. The example of an insecure, black-box backdoorable EC like in this article would have a "building" equivalent of using rebar or concrete of unknown specs and origin and then wondering why the construction collapsed.

Thankfully the liabilities associated with civil engineering means we mostly don't use unknown materials of shady origin and there are multiple layers of review to catch any oversights. The same can be applied to software, and while you're never going to get 100% in either domain, if software was as reliable as buildings (as in you can count the number of major collapses/bugs on one hand in the past few years) it would be a major improvement.

Re:Writing a firmware-only keylogger by kaba0 on Tuesday July 06, 2021 @07:45AM (#27747095)
Disagree. First of all, the level of detail an atomic level simulation could provide is simply useless in the grand scheme of things. Classical physics is more than enough for the vast majority of use cases and they can be simulated by computers. Eg, you can programmatically measure the load bearing on any part of a structure. And the more important thing, engineers can usually fall back to safety margins that “linearly scale” the provided confidence in a given case. What I mean by that, is that if a given part has to be this stable, as per the calculations, you can trivially make it 3x wider.

While a while loop in a computer program will eat away at any sort of redundancy you may introduce, and the complexity of computability itself simply leaves behind even mathematics. There is no universal way to prove a non-trivial property of an arbitrary program.

Re:Writing a firmware-only keylogger by sellyme on Monday July 05, 2021 @09:50PM (#27743500)
> The state space of a complex piece of software is vastly larger than that of a building

Not really, we've just gotten very good at constructing buildings thanks to millennia of experience. We're terrible at writing software.

Re:Writing a firmware-only keylogger by _trampeltier on Tuesday July 06, 2021 @01:15AM (#27744469)
Yes. People forget how difficult it is to produce even a screw or a nail. And then there are way more difficult things like tubes.
Re:Writing a firmware-only keylogger by jcims on Monday July 05, 2021 @10:08PM (#27743587)
This isn’t really fair. Most buildings, public works, utilities and industrial processes are extremely vulnerable to the most basic of attacks, they just don’t get carried out as often in physical space because it’s logistically more difficult to execute.
Re:Writing a firmware-only keylogger by sellyme on Monday July 05, 2021 @10:45PM (#27743775)
Your claim is fundamentally "It's logistically easier to attack software, so such attacks will happen more often".

This is absolutely true, but it's also proportionally easier to defend software. It's insanely easy to test whether your software is vulnerable to SQL injection, it's not particularly easy to test whether your building can be destroyed with explosives.

Combine that with the fact that just about every piece of consumer software on the planet has a laundry list of bugs that don't require malicious intent to reproduce, and I find it very hard to accept that reasoning for software developers absconding responsibility.

Re:Writing a firmware-only keylogger by jcims on Monday July 05, 2021 @11:03PM (#27743857)
Empirical/dynamic testing for vulnerabilities is not rigorous or complete in any any way, and is only viable for a relatively small subset of issues.

I'm only suggesting that holding programmers liable for security vulnerabilities isn't really precedented across any other engineering discipline. That's not to say there isn't tons of shitty software being shipped with reckless disregard for quality, and some reckoning there might be useful.

Re:Writing a firmware-only keylogger by SilverRed on Monday July 05, 2021 @11:21PM (#27743941)
We don't expect buildings to hold up to physical attacks. Most would crumble immediately. Just like most hardware doesn't catastrophically fail through normal use.

Computers are one of the only things we expect flawless defense against malice.

Re:Writing a firmware-only keylogger by _trampeltier on Tuesday July 06, 2021 @01:21AM (#27744491)
Today when computers are connected to the whole world, they have to build safe. The analogy would be, if everybody in the whole world could access the buildings frontdoor. In a such scenario, the frontdoor would, of course, build very heavy.
Re:Writing a firmware-only keylogger by SilverRed on Tuesday July 06, 2021 @03:28AM (#27745178)
This is true but it still does not validate the OP comparison between buildings and software. Software faces a much much more difficult task.
Re:Writing a firmware-only keylogger by dmos62 on Tuesday July 06, 2021 @05:15AM (#27745871)
I agree. Standards or requirements should be enforced, and if there's a failure in the company's infrastructure, a panel should investigate if it was due to negligence or non-compliance with the standards. Also, insurance should be mandatory. If a given online platform was a physical piece of infrastructure like a school or a bridge, current state of affairs would cause an uproar.
Re:Writing a firmware-only keylogger by mschuster91 on Monday July 05, 2021 @04:28PM (#27741532)
> Make them pay billions in damages every time somebody gets hacked because of their negligence.

The downside is companies will lock down their hardware even more out of fear of getting sued. It's utterly amazing this person managed to get custom firmware executing on the WiFi chip... stuff like Intel's or AMD's microcode is digitally signed (and iirc, also encrypted) instead of using a plain old XOR checksum, and I'd argue the world is off a lot less safe as a result.

Re:Writing a firmware-only keylogger by Teever on Monday July 05, 2021 @04:55PM (#27741724)
This natural desire to cut corners by locking down devices will be mitigated by right to repair laws.

With that said, it always irks me when someone suggests regulation as a solution to misconduct by large corporations and someone chimes in "But they'll just misbehave in some other way."

If the entity that is misbehaving has changed the way that they're misbehaving in response to your regulation that means that your regulations worked and that you merely need to continue regulating the offender.

Re:Writing a firmware-only keylogger by SilverRed on Monday July 05, 2021 @11:23PM (#27743945)
Right to repair will not allow us to flash custom firmware on wifi cards. At best it will allow us to buy a new wifi card for when the old one breaks.
Re:Writing a firmware-only keylogger by matheusmoreira on Tuesday July 06, 2021 @07:45AM (#27747098)
Just make it illegal to lock down hardware as well. Now they can't cut corners anymore and will have to actually develop good software.

Just keep making their "clever" workarounds illegal every single time until the desired outcome is achieved. They should have literally no choice other than to make a good product.

Re:Writing a firmware-only keylogger by mschuster91 on Tuesday July 06, 2021 @09:14AM (#27748067)
> Just make it illegal to lock down hardware as well. Now they can't cut corners anymore and will have to actually develop good software.

Sadly that one won't ever happen, the copyright mafia will do everything they can to prevent that. Just look at how Netflix is locking down people on rooted devices.

Re:Writing a firmware-only keylogger by matheusmoreira on Tuesday July 06, 2021 @12:11PM (#27750457)
> Sadly that one won't ever happen, the copyright mafia will do everything they can to prevent that.

We really need to abolish copyright as well. It's the 21st century, copying is trivial.

> Just look at how Netflix is locking down people on rooted devices.

I had no idea. Please elaborate.

Re:Writing a firmware-only keylogger by mschuster91 on Thursday July 08, 2021 @04:23AM (#27769478)
If it can detect rooting, either by presence of common rooting apps or by SafetyNet attestation, you only get lowest quality of video.
Re:Writing a firmware-only keylogger by zionic on Monday July 05, 2021 @04:11PM (#27741430)
Imagine having your cryptocurrency wallet’s private key exfiltrated in this way.

Hell, it wouldn’t surprise me if a few less than ethical NSA hackers are doing exactly that in their spare time.

Re:Writing a firmware-only keylogger by Osiris on Monday July 05, 2021 @05:08PM (#27741841)
You should never type your seed phase on any computer. Hardware wallets will give you a randomized keymap for you to recover a seed phrase without using any of the real letters.
Re:Writing a firmware-only keylogger by justshowpost on Tuesday July 06, 2021 @12:55AM (#27744354)
I read what NSA team was installing free internal modules to Cisco routers in their paid time.
Re:Writing a firmware-only keylogger by johncolanduoni on Monday July 05, 2021 @03:52PM (#27741282)
This isn’t a “crappy product”, unless you consider every product that allows users to provide their own firmware crappy.
Re:Writing a firmware-only keylogger by smcameron on Monday July 05, 2021 @03:51PM (#27741273)
Open source stuff would disappear.
Re:Writing a firmware-only keylogger by swiley on Monday July 05, 2021 @05:15PM (#27741876)
Open source is the only stuff that doesn't reliably leave gaping wholes laying around for years because anyone can pay to have them fixed.
Re:Writing a firmware-only keylogger by kaba0 on Tuesday July 06, 2021 @07:49AM (#27747125)
That’s simply false. I really love open-source but to even imply that it is not a ticking bomb of security is just naive.
Re:Writing a firmware-only keylogger by matheusmoreira on Tuesday July 06, 2021 @07:23AM (#27746886)
Why? There's a world of difference between a rich corporation marketing and selling products to consumers and developers publishing some code on the web. It is obvious to me that society expects a lot more from the former.
Re:Writing a firmware-only keylogger by sonograph on Monday July 05, 2021 @05:08PM (#27741838)
I disagree. FOSS and commercially licensed (and sold) software with EULAs are two very different things, and can be distinguished in whatever legal language implements these theoretical liabilities
Re:Writing a firmware-only keylogger by Karunamon on Monday July 05, 2021 @09:46PM (#27743475)
Open source stuff is typically distributed with a massive all-caps warranty disclaimer. If it breaks, you get to keep both pieces.