[148464] in cryptography@c2.net mail archive
Re: [Cryptography] DNSNMC deprecates Certificate Authorities and
daemon@ATHENA.MIT.EDU (Ben Laurie)
Sun Dec 15 15:30:45 2013
X-Original-To: cryptography@metzdowd.com
In-Reply-To: <993B4DD7-498D-475A-AD65-CD92ED4B201D@kinostudios.com>
Date: Sun, 15 Dec 2013 11:21:20 +0000
From: Ben Laurie <ben@links.org>
To: Greg <greg@kinostudios.com>
Cc: Cryptography <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
On 14 December 2013 00:10, Greg <greg@kinostudios.com> wrote:
> Hi list,
>
> Moving this into its own thread:
>
> DNSNMC fixes the authentication problems previously described, and it
> addresses all of the problems that with the previously mentioned proposal=
s.
> It does this first by combining DNS with Namecoin (NMC), and then by
> encouraging a =93trust only those you know=94 policy.5
>
> =93Namecoin is an open source decentralized key/value registration and
> transfer system based on Bitcoin technology=94.[16] Namecoin =93squares Z=
ooko=92s
> Triangle=94, meaning, it makes it possible to have domain names (and other
> types of identifiers) that are:
>
> Authenticated: users can be certain that they are not speaking to an
> impostor
>
> Decentralized: there is no central authority controlling all the names
As I pointed out elsewhere, Bitcoin (and hence Namecoin) is not
decentralised: http://www.links.org/files/decentralised-currencies.pdf.
> Human-readable: names look just like today=92s domain names
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
