Hacker Newsnew | past | comments | ask | show | jobs | submit | throwawayasus's commentslogin

Does anyone know of any company being found liable for negligence after a hack like this? Is it somehow possible to sue them for being so bad at security?

I have an asus laptop that I use for gaming, most likely it had their cruft running at some point. What would be the most viable path to sue?

It is so frustrating and frightening to take security seriously yourself, to have taken precautions, to find out that your idiotic manufacturer has screwed it up in an idiotic way.

Their update system should never have been designed in a way to make this possible. The negligence it in the design of the system.


Asus was actually sued by the FTC a few years ago over poor security practices in their wifi routers.

https://www.ftc.gov/news-events/press-releases/2016/07/ftc-a...


> The negligence it in the design of the system.

Not sure. It seems like a fairly generic update approach. eg a central server(s) provides available updates, with client software on the PC checking for them.

As a concept, that's what MS and Apple's update approaches (for consumers) do too.

It's just ASUS are extremely incompetent with anything software related, not just security.

Hopefully this, plus the previous fine for their incompetence, gets their leadership to change things in a positive way.


> It's just ASUS are extremely incompetent with anything software related, not just security.

Hardware companies are extremely incompetent at anything software related, we see this in everything from PC's and phones (touchwizz, htc sense) right down to TV's and various IoT devices. I can't imagine what the PC industry would like like if luck hadn't delivered us an open platform.


yes, free software and open-source did wonders and I am so thankful for all the devs who made it possible, thank you!

On the other hand, there is a growing number of insecure and closed IoT garbage devices. It will be common to see a wifi attack coming from a breached water kettle.


That’s why you sign stuff - to proove the software delivered not only came from the right place/server but contains the code that was packed at buildtime. THIS is the generic update approach.


ASUS does sign stuff. The problem here is that they won't revoke the compromised certificates...


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

Search: