On Fri, Apr 27, 2012 at 9:15 AM, ianG <i...@iang.org> wrote: > Easy. Take the hash, then publish it. The data can be secret, the hash > need not be.
That works for git. In particular what's nice about it is that you get copies of the hash stored all over. A similar approach can work for Tahoe-LAFS. If the clients remember the Merkle hash tree roots, you don't need to do any AE nor anything else to authenticate the data. Nico -- _______________________________________________ cryptography mailing list cryptography@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography
