A backdoor in a bed
-
I'm 90% sure it is not a single user. I just don't see how that really affects the security of the product, given that the company that sells it can already do the things the author is saying can be done if you have this key.
To be clear, I wouldn't buy this. I just don't think the SSH key makes it any worse than it already was
-
How old are you? Once you reach middle-age shit starts breaking, even if you're fit which most of us aren't. You'll notice a good bed at forty much more than you will at twenty. By sixty you'll be demanding one.
-
Unless you’re still 2 years old and somehow got on here, 13 hours do you more damage than good. But I’m gonna throw a wild guess out there that you don’t have two kids and a mortgage.
-
Said it for me.
-
Hahaha nahhh I have a spouse I’ve been with forever and we’re never having kids, so we can sleep as much as we want to. I don’t get 13 hours EVERY day, but occasionally we get fucked up on various substances and need a long day of hibernation afterwards. Last night we got about four hours (special occasion party time!) so tonight we’ll probably get 10+ hours of sleep.
-
This was written by Papa Bear himself
-
Guess different life styles have different bed needs!
-
Would you rather one person have access to your device / data to potentially perform malicious actions or multiple people access to your device / data to potentially perform malicious actions?
And if you tell me multiple people, you’re full of it.
-
Oh 100%!
No shade on peeps who want families but that’s not for us. We gon’ hedonistically burn bright until we die. That’s our best life hahahaha
-
on a connected bed
If the protocol was documented and simple enough, and if you could make it talk to your smart home RPi, then one could replace AWS with nginx + a perl or lua module.
-
I agree to an extent, the user already uses a cloud service. So they have to trust the provider.
And as far as a bed goes, I suppose you can't expect the customer to ssh into it if something goes wrong and you have to fix it.
Both seems reasonable to me.
-
I think multiple people already have access to the databases that store the data the device sends. I don't really care whether they get the data from the device itself or from the database.
Similarly, I think multiple people have the ability to make changes to the firmware build and the systems that distribute it. So those people already have the potential ability to gain access to the device.
One person or multiple people having unauthorised access are both unacceptable. I'm saying that the users have to trust the companies ability to prevent that occurring, and that therefore this particular technical detail is mostly irrelevant
-
Yeah, its not unreasonable that you'd have a remote way to access the device to gather debug data with the customers consent. An SSH key in the firmware is a flexible way to do that, so long as there are good controls in place to ensure that it isn't misused.
