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 19:34:05 -0500

Administrador wrote:
IMHO I think the important point here is to add suggested TLDs to opennic infrastructure regardless of Namecoin vs Emercoin advantages or differences.
There is no exclusivity agrrement with one or another.

Completely agree!
This is constructive position, with positive outcome!

So, lets talk about *.coin and *.emc, and the benefit of peer with both

About peering, I see two possible technical architectures:

1. Easy to implements - pure rerquest forwarding:
We run EmerCoin wallet with activated DNS-servers on pair of public-available Internet-servers.
Your DNS-servers forwards requests for our TLD-zones (*.coin|*.emc) to our servers, and receive answers.
In this case, your servers will be run just as "caching proxy DNS".

Constrains of this solution - our servers could be attacked, or network traffic could be alerted.
So, this is not 100% insecure solution.
Also, there is added latency for forward request from your server to our DNS-server.

Pros of this solution: easy configure on your side, and do not needed upgrade wallet, if we release a new version,
with another DNS-behaviour. All upgrade will be performed exclusively on our side.


2. Each your server runs copy of EMC-wallet. Requests to our TLD-zones (*.coin|*.emc) your server forwards
to localhost, and local wallet resolves DNS-request. Also, this wallet can work together with emcssh program, to
support distributed ssh-PKI for your sysadmin groups.

Pros of this solution:
- 100% secure and trustful answer. No way to intercept/alter/block data exchange to localhost.
- No latency, because each request resolved locally, on localhost.
- possibility to run EMCSSH PKI for management public key access to your servers (it will interact with local wallet).
- possibility to store in the NVS somr your shared data, with autosynchronization.

Consts:
- On each server: consumed ~1Gb disk space for blockchain, and ~80Mb ram for running instance of emercoin wallet.
- If we release new version with patch in DNS-part - need to upgrade wallet program on each your server.


Of course, we can start work from architecture [1], and thereafter migrate to [2].
Or, you can propose something 3rd.

I'm personally interested in the opennic relationship with crypto-currency market, it may be benefical for all parts

Very good!
We open to any constructive interactions and common projects, and happy to see you here!
So, if you have idea or plans for future collaboration, we will be glad to discuss and cooperate.
In short words: You're welcome!

You can contact directly to me, or write to group address team AT emercoin.com

Thanks,
Oleg




Archive powered by MHonArc 2.6.19.

Top of Page