Yes, its the way I would've done it. Actually coincidentally I already did propose doing it exactly that way in around 1999: http://www.cypherspace.org/p2p/auditable-namespace.html (That was about censor resistant DNS->ip mapping with public auditability. And that might still be something to think about with the current us governments habit of seizing domains without legal due process. Anyway the same technique should work for public keys ... map a name to its IP address and the hash of its public key, or its public key. My view is that these mappings are global and even with legal due process, you dont want a local legal authority to be able to override a global view. Global views are conflicting. Even somethings that are forbidden in one area as may not be forbidden in another, or may even be mandatory! Local legal conclusions should be advisory for the local area. Adam On Sun, Nov 27, 2011 at 08:12:00AM +0200, Martin Paljak wrote:
No, they had ecc and I saw no references to hash chains or trees. But that would be a right/interesting direction. On Nov 27, 2011 12:42 AM, "Adam Back" <adam@cypherspace.org> wrote:
I only skimmed the high level but I presume they would be using a merkle hash-tree and time-stamp server or something like that so it cant revise its story later and its current state can be audited by anyone against its advertised information.
Adam
cryptography mailing list cryptography@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE