6 ms·
That's exactly where I keep getting caught. I've looked at in-toto a number of times, and each time I've been left wondering "how is this better than a signed l
by marksomnian 2mo ago
That's exactly where I keep getting caught. I've looked at in-toto a number of times, and each time I've been left wondering "how is this better than a signed list of hashes?".
Which I suppose is what in-toto is at its core, but it's taken me a long time and lots of reading to get to that point, and I'm not seeing the advantages of it (except it being a standard, OK, fair enough).
I must be missing something.
- uecker 2mo agoI assume it is meant to not only have hashes of the final output, but also securely record all steps done by the right people and the right inputs during building of the software. But this solves the wrong^1 problems while still leaving the door open for malware. Reproducible builds are the right step forward if you actually care about security of free software ecosystem. 1. I guess this depend on your position. In the context of remote attestation, I think this is also even dangerous / evil.
- Chris2048 2mo ago> In the context of remote attestation, I think this is also even dangerous / evil. It's cool until it becomes enforced and we no longer hold the keys to our own hardware; bwim the ability to determine which key signers are to be trusted. But I don't think standing in the way of attestation tech is a fruitful tactic - much better to fight for hardware/key control.
- uecker 2mo agoThe website / service you want to use will not accept your key, but only the key from the organization that makes sure that your software does not make it possible to skip the ads. So I think the only chance to avoid this is to reject such concepts completely from the beginning.