On Friday, March 9, 2018 at 3:19:47 PM UTC-5, Innovative Inventor wrote: > I was looking at the canaries, and I liked the idea of a proof of freshness > with the latest news headlines. While people can't create canaries ahead of > time, it is possible to conspire to modify or backdate one of them after they > have been published. To prevent this, we could use a blockchain-based > timestamp, where the hashes of each canary are placed within the blockchain > of a powerful cryptocurrency. Something similar to these services: > > https://opentimestamps.org/ > http://originstamp.org/home > > This way, if there ever is a interruption of canaries, followed by a court > order or something forcing you guys to backdate a falsified canary or modify > old ones, we will all be able to check.
Something that I think can also be added to improve the canaries is to add NIST's Randomness Beacon to the proof of freshness by adding the output of https://beacon.nist.gov/rest/record/last.xml. I realize that in most hypothetical scenarios, a government, is the attacker, but it can't hurt to add a government to the list of organizations an attacker would have to attack just to coerce a canary ahead of time. What do you guys think? -- 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/43f4b404-ba2a-45aa-85ef-e0cde6be0ffb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
