Bug 1479: GnuPG curl-shim TCP half-close harms HTTP interop

Bernd Eckenfels lists-gnupgdev at lina.inka.de
Sun Mar 3 21:54:31 CET 2013

Am 03.03.2013, 02:38 Uhr, schrieb David Shaw <dshaw at jabberwocky.com>:
> Ok, this is reasonable.  I'll add some code to gpgkeys to look for the  
> HTTP status.  It'll only really work properly on sks 1.1.4 or later, but  
> it'll work well enough on earlier versions (it'll say "key can't be  
> retrieved" rather than "key not found" if the key isn't found).  That  
> addresses all 4 cases here, since gpgkeys can use those status codes,  
> along with the state it already has, to tell the difference between key  
> found (either complete or incomplete), not found, and server failed.

For an aorted transfer, it is required to check for Content-Length or
Chunk borders. I dont see how the status code would/could help. Since an
aborted transfer still has a status of 200.


More information about the Gnupg-devel mailing list