Namecoin Local PGP Keyserver

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Namecoin Local PGP Keyserver

Post by phelix » Fri Oct 02, 2015 3:33 pm

This idea was brought up by Domob here and was further discussed here.

I just ran across the Skier keyserver (Python): https://github.com/SkierPGP/Skier

It looks like it is too much for this purpose but may be helpful in creating a minimal local server. E.g. to be used in NMControl.

[edited]
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

somename
Posts: 80
Joined: Mon Sep 15, 2014 3:12 pm
os: windows

Re: Namecoin Local PGP Keyserver

Post by somename » Sat Oct 03, 2015 8:19 am

> It looks like it is too much for this purpose but may be helpful in creating a minimal local server

A recent commit makes it possible to "thin" the server: "Allow enabling or disabling of certain, more bloaty Skier features.":
https://github.com/SkierPGP/Skier/commi ... a3896bb1ba

Edit: Maybe the source of this Thunderbird plugin could be modified to talk to Namecoin (instead of OpenLDAP).
Secure Addressing 1.6
by Hiroya Matsuba
This add-on provides features to avoid sending emails to wrong addresses. Key features are a confirmation window of recipient's addresses upon sending, name and affiliation look up at mail composition and main windows, and safe auto completion.

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Re: Namecoin Local PGP Keyserver

Post by phelix » Mon Oct 05, 2015 12:48 pm

somename wrote:> It looks like it is too much for this purpose but may be helpful in creating a minimal local server

A recent commit makes it possible to "thin" the server: "Allow enabling or disabling of certain, more bloaty Skier features.":
https://github.com/SkierPGP/Skier/commi ... a3896bb1ba
That certainly is an improvement. What I had in mind was a very simple bottle request.

Any objections to a bounty for an NMControl plugin?

Edit: Maybe the source of this Thunderbird plugin could be modified to talk to Namecoin (instead of OpenLDAP).
Secure Addressing 1.6
by Hiroya Matsuba
This add-on provides features to avoid sending emails to wrong addresses. Key features are a confirmation window of recipient's addresses upon sending, name and affiliation look up at mail composition and main windows, and safe auto completion.
Hmm this looks more complicated. Also the keyserver approach should work with every mail client.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Re: Namecoin Local PGP Keyserver

Post by phelix » Mon Oct 26, 2015 9:59 am

I had completely missed we already have a bounty for this. Maybe I should take a break.

Still, how would this work? Search the keyserver for id/user and have the keyserver reply with exactly one key? This would mean the keyserver would have to dig through the whole id namespace.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

cassini
Posts: 329
Joined: Sun May 26, 2013 6:36 pm

Re: Namecoin Local PGP Keyserver

Post by cassini » Mon Oct 26, 2015 11:35 am

phelix wrote:This would mean the keyserver would have to dig through the whole id namespace.
This is no big issue, I think. Currently (~5000 id/ records) reading in into a simple cache array takes less than an hour using name_show. Probably much less with name_filter or a new purpose-built RPC. Even if we have half a million ids this doesn't take a lot more time as most CPU time is wasted separating the 600000+ d/ records.
After this cache setup the keyserver could permanently listen to incoming blocks, extract any id content from a new block and update the cache.

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Re: Namecoin Local PGP Keyserver

Post by phelix » Tue Oct 27, 2015 4:21 pm

cassini wrote:
phelix wrote:This would mean the keyserver would have to dig through the whole id namespace.
This is no big issue, I think. Currently (~5000 id/ records) reading in into a simple cache array takes less than an hour using name_show. Probably much less with name_filter or a new purpose-built RPC. Even if we have half a million ids this doesn't take a lot more time as most CPU time is wasted separating the 600000+ d/ records.
After this cache setup the keyserver could permanently listen to incoming blocks, extract any id content from a new block and update the cache.
Actually "name_filter id/" takes only 10 seconds or so. Maybe this is the way to go for now.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Re: Namecoin Local PGP Keyserver

Post by phelix » Tue Nov 03, 2015 8:25 am

The way I assume this should work is by getting the actual key from a keyserver. Tor support could be added but it still is not very nice. Alternatively we could store the key in the blockchain (my pubkey is ~1200 bytes - 3 names/values). Opinions?
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

domob
Posts: 1091
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Re: Namecoin Local PGP Keyserver

Post by domob » Tue Nov 03, 2015 9:24 am

phelix wrote:The way I assume this should work is by getting the actual key from a keyserver. Tor support could be added but it still is not very nice. Alternatively we could store the key in the blockchain (my pubkey is ~1200 bytes - 3 names/values). Opinions?
I think we shouldn't put pubkeys into the blockchain. Instead, I agree with phelix that getting the key from a keyserver over Tor and verifying the fingerprint against the blockchain seems fine. Doesn't the id/ format also allow to specify a link to the pubkey if hosted somewhere? This (if present) could also be used.
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

biolizard89
Posts: 1961
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Namecoin Local PGP Keyserver

Post by biolizard89 » Wed Nov 04, 2015 5:35 pm

domob wrote:
phelix wrote:The way I assume this should work is by getting the actual key from a keyserver. Tor support could be added but it still is not very nice. Alternatively we could store the key in the blockchain (my pubkey is ~1200 bytes - 3 names/values). Opinions?
I think we shouldn't put pubkeys into the blockchain. Instead, I agree with phelix that getting the key from a keyserver over Tor and verifying the fingerprint against the blockchain seems fine. Doesn't the id/ format also allow to specify a link to the pubkey if hosted somewhere? This (if present) could also be used.
Will ECC pubkeys fit in the blockchain acceptably? I think GPG has added support for them in beta versions. (Not certain on this.)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

phelix
Posts: 1631
Joined: Thu Aug 18, 2011 6:59 am

Re: Namecoin Local PGP Keyserver

Post by phelix » Thu Nov 05, 2015 4:23 pm

biolizard89 wrote:
domob wrote:
phelix wrote:The way I assume this should work is by getting the actual key from a keyserver. Tor support could be added but it still is not very nice. Alternatively we could store the key in the blockchain (my pubkey is ~1200 bytes - 3 names/values). Opinions?
I think we shouldn't put pubkeys into the blockchain. Instead, I agree with phelix that getting the key from a keyserver over Tor and verifying the fingerprint against the blockchain seems fine. Doesn't the id/ format also allow to specify a link to the pubkey if hosted somewhere? This (if present) could also be used.
Will ECC pubkeys fit in the blockchain acceptably? I think GPG has added support for them in beta versions. (Not certain on this.)
Yeah they should fit. This would be cool. But with my enigmail I can not create ECC keys so we should probably allow other methods, too, and maybe postpone this a bit.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

Locked