Skip to the content ForoHackers
Log inJoin

I've got two signed firmware releases for our toy boat. They're both telling the truth.

FirmwareSupply chain security
#15366 · · Quote · Report

We made a tiny wooden boat with an LED buoy display for the club. In May we learnt that the instruction leaflet and the firmware can both be signed. This time both files really are firmware. Our versions 1.4 and 1.5 have valid signatures from the same club release key. A friend says the old file should fail verification the day we put 1.5 out. He has already written the chorus to a song about it. I'd like to disagree before he starts work on the verses.

#15615 · · Quote · Report

The old firmware signature can still say "these exact bytes were signed with that key". Deciding which release to run today is a different statement. What does the club actually want the boat to play?

#15616 · · Quote · Report

At normal exhibitions, whatever the current release is. On the anniversary we promised to reproduce the original very bad buoy animation. Which explicitly requires that 1.4 remain itself.

#15617 · · Quote · Report

So call one folder Current and the other Real Current. Someone had to stand up for the traditions of our people.

#15618 · · Quote · Report

guardaría un manifiesto de la exposición de aniversario con la versión que usasteis. no le pidas a la firma que recuerde qué quería hacer el comisario del barquito en julio.

#15619 · · Quote · Report

Also there's no need to revoke a good release key because the song is old. A lost or compromised key would be an entirely different job. The buoy has suffered enough.

#15639 · · Quote · Report

He got as far as "genuine, obsolete and bobbing gently". I have withdrawn my objection to verse two.

#15647 · · Quote · Report

Pregunta seria del taller: ¿cómo decide un voluntario nuevo si arranca el firmware de exhibición o el de aniversario? Si la respuesta es "me reconoce por la cara", vais a necesitarte atado al barco.

#15648 · · Quote · Report

Va una tarjeta con el ID de la edición y para qué se usó en esa exhibición. Si hubiera que retirarla por una vulnerabilidad real, eso tendría prioridad. La boya simplemente era fea, que es un defecto difícil de parchear con dignidad.

#15649 · · Quote · Report

People sometimes need a patch after a firmware vulnerability and a patched image for display. You still keep the historical file as evidence of what shipped. Keeping a file doesn't oblige anyone to install it on a boat.

#15650 · · Quote · Report

Joder, me he quedado escuchando el estribillo en la cabeza y ni siquiera entiendo quién ha puesto a flotar el firmware.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply