Earlier quoted context omitted.
Or you could just implement them as-is, earn a shitload of money and then enhance their security in the next version or with a firmware update once you'll have the luxury of investing in R&D. At least it's better if a security-wary entrepreneur implements them instead of someone who simply doesn't give a flying fuck.
Did you keep a straight face while you suggested that people actually upgrade firmware?
I stayed in a hotel with Android lightswitches and it was as bad as you'd think
51–60 of 325 posts
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#52Earlier quoted context omitted.
Or you could just implement them as-is, earn a shitload of money and then enhance their security in the next version or with a firmware update once you'll have the luxury of investing in R&D. At least it's better if a security-wary entrepreneur implements them instead of someone who simply doesn't give a flying fuck.
Did you keep a straight face while you suggested that people actually upgrade firmware?
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#53The problem is that when a software engineer goes to the front desk of a hotel and complains about the security of the brand new Android-Powered Hi-Tech system that they just put in, the person working the desk thinks, "Haha wow! That nerd was a real Sheldon Cooper, like on the television!" and they don't care at all. If you live in a bubble where programming and computer work is black magic, well then of course it is completely inevitable that someone so nerdy and so smart would be able to hack everything on the planet. So they don't really think there's anything to be done.
When it's a group of annoying little 15 year olds that sneak out in the middle of the night to wake up all of your guests, it's a lot bigger of a deal.
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#54prepare to be arrested for various violations as a punishment for pointing out these obvious and dangerous flaws.
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#55Earlier quoted context omitted.
Or you could just implement them as-is, earn a shitload of money and then enhance their security in the next version or with a firmware update once you'll have the luxury of investing in R&D. At least it's better if a security-wary entrepreneur implements them instead of someone who simply doesn't give a flying fuck.
Did you keep a straight face while you suggested that people actually upgrade firmware?
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#56Earlier quoted context omitted.
That's technical debt, and it's hard to fix. A prototype, sure, it can have flaws, it's a proof of concept of feature X, not feature X SECURED. But then the release has to be a rewrite. If it's not, those flaws are more likely to become permanent. And when they do begin work on repairing their codebase, they'll spend several times the money and time to fix than if they'd spent some time early on. They'll also likely…
Ok, I'll clarify: I think they were right as long as it was a throwaway prototype. And the GET delete operations are probably a bad idea even for a prototype. I was thinking of a rewrite for release 1.x. I don't have enough knowledge of the stage the OP's startup was to have answered, so I stand corrected.
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#57Which takes us to this: "Any sufficiently advanced technology controlled by a miscreant is indistinguishable from a possessed object in a Stephen King Novel."
http://thefutureisastephenkingnovel.com/assets/player/Keynot...
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#58Earlier quoted context omitted.
Did you keep a straight face while you suggested that people actually upgrade firmware?
Keep in-mind that we're talking about always connected devices. Firmware updates could be done remotely without the end user needed to do anything, except perhaps give his approval.
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#59Earlier quoted context omitted.
That's technical debt, and it's hard to fix. A prototype, sure, it can have flaws, it's a proof of concept of feature X, not feature X SECURED. But then the release has to be a rewrite. If it's not, those flaws are more likely to become permanent. And when they do begin work on repairing their codebase, they'll spend several times the money and time to fix than if they'd spent some time early on. They'll also likely…
Ok, I'll clarify: I think they were right as long as it was a throwaway prototype. And the GET delete operations are probably a bad idea even for a prototype. I was thinking of a rewrite for release 1.x. I don't have enough knowledge of the stage the OP's startup was to have answered, so I stand corrected.
Re: I stayed in a hotel with Android lightswitches and it was as bad as you'd think
#60I'm amused by the use of Modbus. I worked on Modbus networking back in the 1980's at Modicon (a company that disappeared long ago that created the "standard"). Using a protocol invented before the internet to control devices on a semi-public network is insane. The original Modbus was designed to communicate with factory devices controlled by logic controllers over serial and eventually over a custom token ring networ…