-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, everybody.
I have been following SKS mailing lists for years and I wonder how can
OpenPGP rely on an undocumented protocol, with only a single codebase
written in a unusual language for something so paramount as keyservers
and key distribution :-).
http://minsky-primus.homeip.net/sks/
I don't have a bad eye for SKS. I think it covers a badly needed need
and it is not its fault if there is no competition. I read the master
thesis that was seminal writing for this project, but the exact
protocol is not documented and must be digged from the sourcecode...
written in Ocaml :-).
I am really uncomfy with this situation, and I wonder if I am
overreacting, or people are not actually aware of this "monoculture"
and lack of interoperativity...
Please, consider this *NOT* an attack to SKS (thanks god we have it!)
but a heads up to think about it.
- --
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
jcea(_at_)jcea(_dot_)es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/
_/_/
jabber / xmpp:jcea(_at_)jabber(_dot_)org _/_/ _/_/
_/_/_/_/_/
. _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQCVAwUBUOXmrplgi5GaxT1NAQJE/gQApktUxJ2pMJmlNKADeOUdEIQqDcklW3LG
lA52an7QuSFZ4JijFYMMXB+IOkQ0CQU9sghYZw63ZciLr3Y6bYKYCRgEFUGyF4hH
/FiTmlUaQYEgrFPYSmQ0/ZHxiiFs9tVjmid1khBJTvsHNmhIvxbD0n4qZbp5p70g
gfYrgLr0MPQ=
=HCAJ
-----END PGP SIGNATURE-----
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp