-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2014-02-19 23:12, Robert J. Hansen wrote:
It's not necessary that it become official. After all, the HKP
keyserver protocol isn't documented in RFC4880. It's just necessary
that it become a de-facto standard way of querying for keys. If/when
it
becomes a de-facto standard, GnuPG will quickly add support for it as a
keyserver protocol, and Enigmail will follow suit.
I'm not a developer either. That said, when I look at namecoin, I see a
mess that is a long ways from widespread support. The bitcoin protocol
(upon which namecoin is based) apparently has problems, which I *don't
think* impact namecoin, but suggest that bitcoin itself needs to mature
a bit (which has implications for all of its derivatives).
All that said, I'm a bit confused by this. GnuPG *does* support the HKP
protocol with the keyserver option.
-----BEGIN PGP SIGNATURE-----
Version: OpenPGP.js v.1.20131017
Comment: http://openpgpjs.org
wsFcBAEBCAAQBQJTBa//CRAVeuMeEjZgKwAA888P/jE5vYBfBURV4FwvUSnI
jVZrSCtHnzg0uVxTfzb6wHWcFuMwEPHAWFOenPozxmIO7qrDviPoBTREShpa
5f7H8x6u5d0JYNxX0omVYthTcsijZmUx+e7xy5Kg7hV4XCZPNCx21lMzq17u
qGMXH4njNxjzBNJleeXNz4Wn7q+dAuNOI5Pm+GDySIbCSV3OhcWNZZu9l4SC
1BKYfxGf0mZRVv9VhyLNeMzYes5btRgAtnm5rviTn/5MfJ2+chVKomMxe6BP
R9MakW1i4Re4XUzBxDPxbZpDbyQjqCLSR3MiNEt5P+Q2mf88iX9WYGUk2pKh
APdLItjXXvR+Ha0yGjH26lHa1RDzOdRopF+IQCdATT4rNrHthtYup1qRjVTo
/znVTqbpWnAanGWSw0oRRVAqfseQA3enfpPIiVCVIBIIUweMmHsZNyt9Bewd
aGGL0keWnrkThqvuTB0CQAJPhBk6CqTaFfn8Z4sj+4iM+QoeCkBoUnwPuYc+
koQABsDP9gRKg1CPb9rqzcVI2A9Vr3bCjew/MkM1/jiRgtAYtJJTQKZGJZ/e
hmGoYPZ4q0ynOKE3hDvm89hlUSk5e5qZRGsh/yyMuAP90TipzdjEg0ZWPQYy
hUjC0AQlgbpdUxAHVDQWziNDVJifrhm8JPVwMqLVGbQjMB29qfhAlBUe6Pic
LFQ6
=sRQQ
-----END PGP SIGNATURE-----
_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
