Hey all-- If you look at https://pgp.mit.edu/pks/lookup?op=get&search=0xF2AD85AC1E42B367
it appears that there's some sort of proxy failure.
the end of it looks like:
-----------
VcZqMYLvC976Pel/3NSXRKBrgVVWvoiEvH/Zaxxy1RjpRBWomzGInAQQAQIABgUCVu5/IwAK
CRA+Efo9IPZM80EQA/9xJ2QKliIrKvAnWejhEEGmJvph+XWbBkwEHHTEnhMqpeZx1OJYwqpp
CmWVVaXxY4ch8nNOvs3F0qPCZ3FkM1Zr4ghxfL2ir+or+4N8j1MyX0lkEtsbyG0AumTjXz+4
NKO9Sw+KsjBDhOlJsokKLQ3gpHTTP/1.0 408 Request Timeout
Server: sks_www/1.1.5
Cache-Control: no-cache
Pragma: no-cache
Expires: 0
Content-length: 599
Content-type: text/html; charset=UTF-8
Access-Control-Allow-Origin: *
Time Out
Error handling request (GET /pks/lookup?op=get&search=0xF2AD85AC1E42B367):
Timed out after 1 seconds
-----------
I don't know what kind of reverse proxy is in place here, or why it's
behaving in this way, but it doesn't seem like this is a healthy
keyserver (at least for larger keys like this one).
Any thoughts on how we should check for or fix this kind of failure ?
should we pull pgp.mit.edu from the pool until it's resolved?
--dkg
signature.asc
Description: PGP signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
