News for hackers. Stuff that matters.
Re:Unsafe at any clock speed: Linux kernel security needs a ... by FussyZeus on Tuesday September 27, 2016 @07:33PM (#12594208)
As important as security is, and as much as I think Linux should be secured more proactively, I have to take issue with two things mentioned:

1. Most devices are not administered by IT Professionals

This is true and must be taken into consideration, but while every layman can't be a sysadmin, neither can you, I think in 2016, simply take a position of "I don't need to understand any of this, and everything should Just Work." I don't think that's realistic, if you want the home automation we see in the Jetsons, if you want smart devices in your home setup to make your coffee at exactly 5:56 AM, then you need to step up and take a little responsibility for learning how this stuff works and how to set it up. Now is it realistic for end users to perform kernel updates, testing functionality, and changing out for new packages as needed? Of course not. But a basic understanding of the underlying technology helps in a long way in troubleshooting the inevitable problems that will arise, and in letting you choose, intelligently, what OEM's to do business with.

2. Manufacturers leaving devices un-updated, unmaintained after production

This is asinine, especially for the devices that require online connectivity. You already have a more-or-less constant WAN connection, so why on Earth can't these devices update their firmware when required? The answer is of course that after-sale support is not profitable but that too is unacceptable, if you're going to bake computers into your products, you as a company need to step the hell up and support them, not just throw them on the market for a quick buck and then run away with the cash.

My 0.02.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by drvdevd on Tuesday September 27, 2016 @08:56PM (#12594632)
Android is probably a good example of the update problem in action, but it's hard to blame Linux directly for this. Rather it is indeed the product cycle that seems to be driving the problem as you point out in #2 there. But then again, isn't it reasonable to expect some sort of deprecation or end of life for most products?

Also, even if manufacturers are held to account more, we will still see severe bugs, IMO, in Linux or even some hypothetically more secure, future OS.

As it's framed in this article at least, I think the automotive manufacturer metaphor falls down at some point (even if most cars now run Linux too). I think software is just vastly more complex and we are just now learning how to cope with that complexity.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by pjmlp on Wednesday September 28, 2016 @03:05AM (#12595930)
> I think software is just vastly more complex and we are just now learning how to cope with that complexity.

If an engineer builds a bridge and it falls down, s/he will get punished for it.

If a doctor or a lawyer makes a similar hard mistake, s/he will get punished for it.

The same needs to happen to software engineering, specially given that in most countries software engineering is a degree with the respective Engineering Order.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by drvdevd on Wednesday September 28, 2016 @06:04AM (#12596529)
I agree that liability has its' place in software engineering. But I don't think, at this point in history at least, we can apply it broadly across the many subdomains thereof.

For example, we can't hold Linus Torvalds liable when the Linux Kernel has a bug (perhaps not even if it was deliberate!). If we even tried to, the entire project would likely come to a screeching halt.

How is this model of liability compatible with large open source codebases?

Re:Unsafe at any clock speed: Linux kernel security needs a ... by ex_amazon_sde on Wednesday September 28, 2016 @08:54AM (#12597249)
> How is this model of liability compatible with large open source codebases?

Yes, like in other fields. Obviously people are not chased out of town for as small error.

It's when people conspire together to hide big problems that liability becomes important.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by drvdevd on Wednesday September 28, 2016 @09:30AM (#12597430)
Agreed. Which, as evidenced by the recent emissions scandals, is a quite realistic scenario.
Re:Unsafe at any clock speed: Linux kernel security needs a ... by pjmlp on Wednesday September 28, 2016 @07:32AM (#12596876)
No, not Linus but the ones that caused the failure.
Re:Unsafe at any clock speed: Linux kernel security needs a ... by FussyZeus on Wednesday September 28, 2016 @08:09AM (#12597031)
Why would Linus be responsible? That would be like holding Sir Henry Bessemer (inventor of steel) responsible for the Tacoma Narrows bridge. Of course it wasn't his fault: his contribution was used incorrectly, as Linux is frequently used incorrectly by IoT companies.

And frankly, if your thermostat malfunctions and runs your heat full bore for a weekend while you're out of town, I don't think it's unreasonable to say that, assuming basic requirements were present for functionality (power, connectivity to the furnace, etc.) that the company should be responsible if their system went wrong solely because of poorly designed software. If for nothing else than your outrageous heating bill.

And again, if a company's response is "well we don't want to be responsible for your furnace" then my response is "then don't be making fraking thermostats, because that's what they're FOR!"

Re:Unsafe at any clock speed: Linux kernel security needs a ... by drvdevd on Wednesday September 28, 2016 @09:26AM (#12597411)
I absolutely agree and that's exactly my point: although Linus shouldn't be held responsible, when your IoT thermostat breaks, that still doesn't mean the breakage hasn't been a trickle down result of some technical decision he made at the kernel layer (if it was a kernel bug that caused it anyway). But it's an open source project and he makes the rules and companies have a choice as to whether they want to adopt it.

So I would agree that in this hypothetical case, the IoT company needs a custom kernel patch on their device, and hopefully it gets upstreamed.

But if all this occurs after your furnace is shot, you're left asking the manufacturer, "Why did you use Linux at all in this product?" You would think they'd then accept responsibility but what if they do try to blame the Linux project and have expensive lawyers to back them up?

This all seems to add up to a potential spaghetti mess of blame where the legal model is "doctors and lawyers and bridge builders." In fact I think these problems need to be addressed outside current legal and regulatory systems which frankly can't keep up with the pace of open source software.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by FussyZeus on Wednesday September 28, 2016 @12:47AM (#12595462)
> But then again, isn't it reasonable to expect some sort of deprecation or end of life for most products?

In a cell phone? Sure, because the replacement process is a somewhat annoying sales appointment at $carrier. In a thermostat? No, because it should last years. Maybe decades if it's a good one. IoT falls apart in this arena because the hardware is designed to be replaced often, and that's exactly what house hardware should not be.

And if the software is too complex, then don't do it. Do it right or don't bother.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by caf on Wednesday September 28, 2016 @01:09AM (#12595544)
I wonder if the solution for IoT things like the network-connected door lock mentioned in the article is the emergence of third-party companies that are contracted by the initial manufacturer to provide ongoing updates for the expected product life (eg 15 years).

The idea being that these patching companies would become recognised brands, and the manufacturer would get to put a "Supported by FooCorp until 2031" badge on their packaging, and consumers would start to expect to see this.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by FussyZeus on Wednesday September 28, 2016 @08:12AM (#12597044)
My other thought relating to what you said would be why on Earth does a door lock need Linux? This is not exactly a massively complicated device, it controls a 2-state mechanism and needs to work at about a five foot radius. The fact that something like that, in an IoT mindset, needs an entire webserver is ridiculous. This is much more suited to a micro-controller with custom firmware and a tiny attack surface.

No, maybe you won't be able to set it up with a smartphone and 2 minutes, but it also might WORK BETTER if it wasn't able to do that.