trillian-examples

>This feels like this might actually be a use-case for a blockchain or a Merkle Tree. A few years ago, a similar idea for firmware binary security[0] had been explored by Google as a possible application of their Trillian[1] distributed ledger, which is based on Merkle Trees. I don't know if they've advanced adoption of Trillian for firmware, however, the website lists Go packaging[2], Certificate Transparency[3], and SigStore[4] as current applications. [0] https://github.com/google/trillian-examples/tree/master/bina... [1] https://transparency.dev/ [2] https://go.googlesource.com/proposal/+/master/design/25530-s... [3] https://certificate.transparency.dev/ [4] https://www.sigstore.dev/

Recently I developed a presentation* about immutability as a design concept in computer security. As part of it, I have slides which cover Certificate Transparency implementation[0], which uses Trillian[1] as a distributed ledger. Part of Trillian's documentation includes a Firmware Transparency[2] example. For the year or so I've been aware of it, I've thought that it's a great idea, and wondered if it would ever grow as a project/practice. Digging through the links in this announcement, it appears Trillian is the basis for the distributed ledger here. Glad to see the idea has been taken further by Google! * Sorry, the presentation is non-public. [0] https://certificate.transparency.dev/ [1] https://transparency.dev/ [2] https://github.com/google/trillian-examples/tree/master/bina...