pgp key servers cors support
Kristian Fiskerstrand
kristian.fiskerstrand at sumptuouscapital.com
Sun Apr 20 18:37:43 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 04/19/2014 11:40 PM, tim at piratemail.se wrote:
>
>
> Greetings,
>
> I believe I asked a pgp key server http interface question on this
> list a while ago, and received a useful response.
>
> I also wrote tobug-pks at mit.eduwith the request below.. With no
> response.
For questions regarding keyservers, sks-devel[0] is probably your best
bet..
>
>
>
> Is there any way that the http pgp key servers could be changed to
> provide cors headers allowing access from any site? This could
> also be done through some proxy server (njinx?) which accepts,
> forwards and then concatenates cors headers to the response.
This is alreday included in the SKS trunk as of commit [1] for an
upcoming 1.1.5 release. Once that is released
subset.pool.sks-keyservers.net[2] will be bumped to this as a min
requirement and can be used for your purposes.
>
> I realize this is not the pgp keyserver mailing list. But I figure
> the developers of that server also reside in this list -- and I'm
> not sure exactly which list is the right list to post to.
>
References
[0] http://lists.nongnu.org/archive/html/sks-devel/
[1]
https://bitbucket.org/skskeyserver/sks-keyserver/commits/f6e4e88a049a3497cc17b0ad15530782d78bc59f?at=default
[2] https://sks-keyservers.net/overview-of-pools.php#pool_subset
- --
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
"I have always wished that my computer would be as easy to use as my
telephone.
My wish has come true -- I no longer know how to use my telephone"
(Bjarne Stroustrup, April 1999)
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJTU/fUAAoJEPw7F94F4TaggwwP/jNtYKU4h27XPGudP8GmxKF3
0MIYyXUYqQElcHyNl/Ji/hcCrILZ8bj2XCyxMvulNEvNs23lLxCccziL0t8FKCOG
iralbpjwszSqmeKsuZ1dr5ZsG2DzOvqgLz3d/k1pRSo3XHwmB4rlvM3W++hlwT/A
sYNizJVwrQ2OdZSApnnufub4b0VNcTvIIalMDnkAtI43Dk4hL1gFaPEpbnLneExd
lDDcUKDyqudBi7oNvQhS8nIGiPOp4cmU/+AJy5nU0NoNTJ60CYBO97TIifgWJuY5
Dwt6aSEoXZTraIS0tlEWguzY3Le4ztY/8ho9HSKgKSshatCq5z2LUfpZpVZvBQ3r
vK4fgK0uGpHm1oz9ah9V0lH1nWnSWKYvDldrm44k9PJ3F7zl3gSSAGi+A+2OFqGY
mDVrFmidLUEztKnD0hw7Hee1Ooj36EUBkYxhTGdGxDLzvY7ZKkq7so6stsc4FmSj
mhOw10ju1SF8Ag1dWe3VH+H22dsukU6B+ZgEKlKRnO0R2ZPFJ08ik/WiKBjyJ+N9
cveOxZeIKGsb/urJtR8ExTLt3fVW7ampDRlz0624FcGc4ETY54x/tEDQWD9XEN37
haM9MWr8xTQR5katIwnq80h1xSpEJVvoBi+8jWI6C9LyW8TGD9fb+lw87lRbTFkt
rCzcQ3DejmyS82DZCZrh
=Rp3p
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list