3 ms·
I don't think every user has to reproduce the build; it should suffice to have a handful of verifiers building and checking the published versions. Someone need
by yjftsjthsd-h 3y ago
I don't think every user has to reproduce the build; it should suffice to have a handful of verifiers building and checking the published versions. Someone needs to do it, but not everyone.
(Edit: yes, you do need a way to make sure everyone is seeing the same published hashes; no idea how to do that)
- hardwaresofton 3y agoYup, thought it was clear in my comment, the software producers should be building and signing THEIR copy from their machine. Seeing the same public hashes can work just like people check shasums now, also possible to independently verify at any time
- woodruffw 3y ago> Seeing the same public hashes can work just like people check shasums now, also possible to independently verify at any time “Verify at any time” devolves to “verify never.” Verification needs to be mandatory to have any security value, which comes back the original point about operationalization.
- woodruffw 3y ago> I don't think every user has to reproduce the build; it should suffice to have a handful of verifiers building and checking the published versions. Someone needs to do it, but not everyone. This works, but you still need a gossiping mechanism (and accompanying threshold model, etc.). That gets very complicated very fast!