Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] EmerCoin: DNS peering and SSH PKI

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] EmerCoin: DNS peering and SSH PKI


Chronological Thread 
  • From: Oleg Khovayko <khovayko AT gmail.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] EmerCoin: DNS peering and SSH PKI
  • Date: Fri, 28 Nov 2014 13:34:21 -0500

Quinn Wood wrote:
MX records with priorities are potentially available through Namecoin's
service record.
Potentially or really?

In addition, I would like to say: Namecoin created distributed storage for DNS, but without native DNS-retrieval mechanism.
We did that. Emercoin wallet "speaks to DNS network on native DNS language", without extra tools.
This is provide seamless integration.

> About a month ago I saw a discussion about storing and fetching SSH keys using Namecoin.

1kb is enough to store current SSH-keys, but is not enough to store future ssh keys. For current world, secure ssh RSA key is 4kbits size.
This is ~800 bytes - pretty close to NMC limit 1kb. And, every ~5 years, key size increased by 1kbit - because of grows computer power and attack efficient.
Thus, in ~5-10 years NMC system will not able to provide enough room for secure keys.

No sense to design and build new PKI, which will reach it's technical limits in ~5-10 years.

And again: You saw _discussion_.
We already have _working_system_, ready to use right now (and we're using it).
I hope, you can understand difference.


20K is a lot of data, and as far as I can tell it's not widely used in
standard DNS.
1. TXT field(s) can be long.

2. We goes another way, than Namecoin. They designed their system primarily as distributed DNS.
And, thereafter trying to use it in another applications.

We created general purpose Name-Value Storage, NVS. This is isolated basic layer.
And, over this layer, we built two practical implementations:
- Distributed DNS (inspired by Namecoin, yes)
- emcssh - world-wide ssh PKI.
In the doc, we defined another possible applications, whose we or someone else can implement on NVS-basic:
gpg, enum, tts, kx, etc.

Why is a distributed store like Namecoin or Emericoin better if it has this?


Why is better? 1st question - better than what?

But, we would like to say: blockchain (EMC or NMC) provides two great and important features:
- distributed certification for all stored information, without CAs.
- worldwide data synch mechanism.

By our opinion, NMC is limited technologically, and their service is deeply linked to DNS only.
We designed 2nd generation, with two layers stack:
- management/transport/certification layer (NVS)
- application layer (DNS, EMCSSH, etc)

And again: We are not contra to Namecoin and it's way. Maybe, they are right, and we are not.
They handle their DNS zone *.bit, and we do not wish "break in to their territory".

Good wish, and good luck to their business.

But, we created our system, and by our vision, it has it's own area of usage.
DNS - only small, practical and obvious implementation. No more.

And, in original letter, we just ask peering to our DNS-system, too.
Why not? Or Namecoin has monopoly for p2p coin-DNS?

We think, OpenNIC - is open structure, and we think, there will be place for everyone -
for NameCoin DNS, EmerCoin DNS, or maybe another interesting systems.

And, as gift, we propose to use emcssh for free. Take and use. Again - why not?

Oleg




Archive powered by MHonArc 2.6.19.

Top of Page