Hi Marek, On 18 March 2018 at 23:12, Marek Marczykowski-Górecki < [email protected]> wrote:
> To be honest, I don't think we need more proofs of freshness there. We > already have various news headlines (chosen from different countries), > bitcoin blockchain and now NIST Randomness Beacon. What we might need, > is timestamps - proof that canaries (or other files there) were > created at the time included there, not later. > What about including the hashes of all older canaries in the new one? That way, anyone trying to counterfeit an old canary would have to somehow hide all of the newer (real) canaries from the victim. Kind regards, Andrew -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CAAXZBWL3E%3D8CTVcGSBfEEBiMBaDL_%3DUSziDY%3Dz_ENEsOuHAdUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
