Namecoin Forum

Hi, I want to propose an idea for an identity management system: |----> 3x Paper-Receipt with QR-code and OCR-B-Text as backup Offline Asymmetric Key-Pair Generator (Hardware) ---->| |----> USB-Security-Token (Hardware) --> User Application (Hard-/Software) <--> Namecoin-Blockchain with Identity-Wal...

Of course, the Namecoin-Qt GUI's future is unclear; there is some uncertainty of whether we'll continue to maintain the name management GUI in the Namecore rebase, or whether we'll switch to Armory (which has a much better GUI). The code in the current Namecoin client is definitely being scrapped t...

I agree with Daniel that application-specific features do not belong in namecoind or libcoin. You can outsource the generation and registration of a X.509 certificate into another wallet, of course. In my opinon buying Namecoins is already a complicated entry barrier. Aside from code redundancy use...

I've hacked together example code to generate a self-signed X.509 client-certificate. It needs a lot of love (charset, catching errors, ...) but it produces a X.509 certificate in PKCS12 file-format which can be imported into Firefox. I also prints the sha256-fingperprint of the certificate. Namecoi...

If it produces data that needs to be written to a name value, then that would require modifications to NMControl to allow write operations. I'm not necessarily opposed to that, but it would require careful thought. Only Namecoin needs to register the fingerprint of the X.509 certificate in the bloc...

Using bool verifyCertificate(X509 *certificate) {} in libcoin would allow us to adjust the dataset/verification process without breaking API-compatibility with verifying applications. If a public key is used for verification it would be a simple comparison with the blockchain. If a fingerprint is us...

I just considered to use the certificate public key instead of the fingerprint as it would allow new encrypted transport protocols to use the public key directly without an unencrypted certificate handshake. But I assume this would bloat the blockchain and have negative scaling effects ...? What do ...

Two new suggestions: Instead of a button per identity in the "Manage Names" table I suggest the options "Create and add/replace client certificate" and "Delete client certificate" in the context menu per identity as we need to disable/delete a client certificate when compromised or lost. libcoin: Ad...

I've found Domain Name Specification and Identity in the Wiki.
Where do I create an entry for a generic application?

In my opinion this is an unnecessary redundancy. As blockchains are decentralized we should drop the idea of the hierarchical client/server paradigm and consider each user/client/server as an equal node. We only need the client/server language to explain it to the IT-dinosaurs! ;) @domob: What do y...