Smart Lock Firmware Update locks out Users
« prev   random   next »

0
0

Smart Lock Firmware Update locks out Users

By TwoScoopsPlissken following x   2017 Sep 3, 8:52am 466 views   5 comments   watch   sfw   quote     share    




Oh Disbeliever in the Techutopia. Hydrogen Cars are coming and so are Solar Roads.

Right after our WiFi Smart Lock that just installed a flawed firmware update is replaced via shipping. Sorry if you used it to lock something important, like the door to your house or garage. 1-2 weeks for a fix.

Even funnier: The exact model was used in a partnership with AirBNB Hosts.

https://arstechnica.com/information-technology/2017/08/500-smart-locks-arent-so-smart-anymore-thanks-to-botched-update/
1   Booger   ignore (0)   2017 Sep 3, 9:44am   ↑ like (2)   ↓ dislike (0)     quote      

Internet enabled locks, what could possibly go wrong?

You would have to be pretty stupid to trust such a device.
2   Booger   ignore (0)   2017 Sep 3, 9:50am   ↑ like (2)   ↓ dislike (0)     quote      

I bet that the coding error was made by a H1B, or someone for whom it's their first job programming.
3   HEY YOU   ignore (7)   2017 Sep 3, 9:55am   ↑ like (0)   ↓ dislike (0)     quote      

Merriam-Webster.com
key:
a : a usually metal instrument by which the bolt of a lock is turned
4   Patrick   ignore (0)   2017 Sep 3, 10:07am   ↑ like (0)   ↓ dislike (0)     quote      

Yes, seems like a spectacularly bad idea to trust and rely only on the internet for access to your own house, but that lock looks like it also would work with a key:

5   TwoScoopsPlissken   ignore (0)   2017 Sep 3, 10:18am   ↑ like (0)   ↓ dislike (0)     quote      

Patrick says
Yes, seems like a spectacularly bad idea to trust and rely only on the internet for access to your own house, but that lock looks like it also would work with a key:


Seems that that model was part of a promotion with Air-BNB, specifically so keys weren't needed.

I wonder how many 'guests' of Air-BNBs just realized their host is 3 states away with the key.

Comment as anon_384e7 or log in at top of page: