Airbnb's preferred smart lock vendor accidentally bricks 500 door-locks

Re:Airbnb's preferred smart lock vendor accidentally bricks ... by Duhck on Monday August 14, 2017 @02:50PM (#15011403)

This is the common (and correct) solution.

In this scenario, the biggest problem is updating the bootloader, which cannot do this type of fallback.

Generally people avoid updating the bootloader (for good reason) but it is necessary sometimes...

[ Parent | on HN ]

Re:Airbnb's preferred smart lock vendor accidentally bricks ... by sliverstorm on Monday August 14, 2017 @06:49PM (#15013725)

Of course, the good thing about the bootloader is it is less likely to need updates in the first place, and it's also likely easier to verify an update with a high level of confidence, as its functionality is so tightly bounded.

[ Parent | on HN ]

Re:Airbnb's preferred smart lock vendor accidentally bricks ... by com2kid on Monday August 14, 2017 @05:47PM (#15013298)

Have two bootloaders, one is trivially provable and can always be relied on in case the entire world falls apart, and can never be updated. The second one is updatable if needs be.

[ Parent | on HN ]

Re:Airbnb's preferred smart lock vendor accidentally bricks ... by striking on Monday August 14, 2017 @04:31PM (#15012572)

Right. It's important that you leave as little logic in your bootloader as possible.

[ Parent | on HN ]