Namecoin Forum

Chrome users simply cannot obtain good security/privacy due to problems with Chrome and Google. This is not something that I can fix. As a result, I don't have much interest in working on Chrome. If someone else wants to implement something like Convergence for Namecoin on Chrome, they're welcome t...

biolizard89 wrote:Talk to phelix about the Mac binary.

I'm not sure what the proper way of contacting him is. phelix: you're free to PM me if you're interested in a Mac build.

So to my ear it is exactly as I said: clients use these notaries in a manner similar to "third-party DNS servers" that they trust. You specifically said "ala your Convergence model". Notaries are not my model, nor have I ever endorsed them. It is therefore definitely not "exactly as you said". Plea...

For end users the wiki is being phased out in favor of namecoin.info. I intend to make sure that this info is reflected on namecoin.info. Cool, is this the new "official site" for NMC? I notice it's missing a Mac binary of a build of namecoinq.git. If you need one let me know. I can also send a pul...

Upstream Convergence uses a locally generated CA cert to make verified certs appear legitimate to Firefox Upstream Convergence (UC for brevity) relies on third-party notaries, does it not? That's what it says after all: "Each notary can only make security decisions for the clients that have chosen ...

It does not provide any functionality which Namecoin's d/ namespace does not provide. It just makes Namecoin's d/ namespace somewhat more interoperable with DNSSEC-supporting software. Gotcha, thank you. As I'm somewhat of the opinion that DNSSEC belongs in the pooper (for the good mankind), I gues...

As far as I know, p/, a/, tor/, and i2p/ are deprecated in favor of id/ and d/. This should be made more clear in the wiki. Oh nice. If that's true then I hope someone updates the wiki. I feel as though I'm too new to this project to do that myself, I'd rather someone who feels more confident in th...

biolizard89 wrote:With Convergence, the pinned cert is trusted because it's generated on your own computer. You can't do that for a third-party DNS server....

Huh? Convergence has "notaries" that you must trust. These are effectively "third-party DNS servers", are they not?

DANE specifies a "TLSA" record for DNS, which contains a TLS fingerprint. Basically the same concept as the "fingerprint" or "tls" field in Namecoin's d/ namespace. It usually only is useful in the context of DNSSEC, but if you're running your own DNS server with namecoind as a data source, it shou...

The DNS protocol is inherently insecure for Namecoin purposes. Using secure lite clients would be a much better option, as you would be certain that names are authentic. Yes, as is, it's insecure, but I'm not referring to using it as-is, just referring to the need for DNSNMC servers and their poten...