Hi Kurt, curl 7.25.0 was released yesterday and I'm now working on updating the Debian package. A problem come up though with the --ssl-enable-beast new option of curl (which should fix the bug that you have reported) and the new version of openssl. If I build curl against the current version 1.0.1-2 (uploaded a few days ago) of libssl the option has no effect with the URL you posted above and curl fails with the error:
curl: (35) error:140773F2:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
unexpected message
(the 35 means that the error happened in the SSL handshake).
But if I build with a slightly older libssl (1.0.0h-1) the option works
as expected and if the option is not used at all the error is the same
that you reported ("Empty reply from server").
Now, since you did the openssl uploads, do you know of any change in
openssl that may have caused this problem and if there's anything that
can be done on the curl's side to fix it?
Cheers
--
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
