3 ms·
This is a good hack, even with some very light abuse (once per 12 hours) of CT logs. I don't see the need to build new tech though. It should be trivial to bui
by anilgulecha 4y ago
This is a good hack, even with some very light abuse (once per 12 hours) of CT logs.
I don't see the need to build new tech though. It should be trivial to build a CRUD layer over git repo (which uses a merkle tree DAG) - and you get public logs to boot, including simple hosting and wide tooling. Immutable commits maintained in a public tree. This could also be combined with the above hack (using commit id).
- michaelmior 4y agoI'm confused how a git repo would help. You can easily write commits in the past. e.g. git commit --date="10 day ago" -m "Your commit message"
- sam_lowry_ 4y agoOnly to the HEAD. If you publish the repo somewhere that does not do garbage collection, this can work.
- transpa-regency 4y agoIf you have a third party sign your git commits, you no longer can no longer modify the commit later undetectedly. And if someone puts their log of signatures into another git repository, you can create an entire web of timestamped trust. https://netfuture.ch/2022/02/git-pgp-blockchain-comparison/ https://netfuture.ch/2022/02/git-pgp-blockchain-comparison/
- michaelmior 4y agoThis is true. Although now this is starting to pretty closely approach what the OP is doing, just using another store for the signatures instead of the CT log.
- michaelmior 4y agoWhy does the fact that you can only do that to the HEAD matter? I can still fake any time in the past. Also, I'm not aware of any public host that does not do garbage collection. But even if that were the case, you still need to trust whatever the repository host is.