Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Wait, are you suggesting using public key fingerprints instead of easily memorized names? Just like onion addresses?


Please note the word "plus" in the comment.

s/instead of/in addition to/

For example, DNSCurve-enabled nameservers are in the form key.name.tld, cjdns addresses have a key fingerprint embdedded in the users IPv6 address, etc.


That little word changes my option on this proposal.

> cjdns addresses have a key fingerprint embdedded in the users IPv6 address, etc.

Very cool idea! I'll read more about this...


I highly recommend reading the excellent draft document from Usenet at the URL I posted, particularly the example of the "Western Wisconsin Computer Company". It is much clearer than my comment and my examples of the simple concept explained therein are probably not ideal (maybe even wrong).

As for cjdns,

https://github.com/cjdelisle/cjdns/blob/master/doc/notes/cry...

From only a cursory review, I see cjdns as a network where one does not need a third party to: issue a name, issue a key, check a key against a name or a name against a key. Each user creates their own private key, their own public key and finally their own address from their own public key. Unless I am mistaken, users get public keys and addresses from other users, not from a third party.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: