Just noticed that the failure above is very slightly different; it
prints "unexpected message" rather than "illegal parameter", although it
still goes away if you manually specify --sslv3.
I have servers which generate the "illegal parameter" error too, but
unfortunately they're not generally acce
The URL mentioned in the original Curl thread
(http://curl.haxx.se/mail/curlphp-2008-10/0001.html) still fails in the
same way
$ curl https://www.etisalat.com.eg
curl: (35) error:140773F2:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
unexpected message
$ curl --sslv3 https://www.etisalat.com.
Public bug reported:
Binary package hint: nagios3
http://labs.opsview.com/2009/10/nagios-scheduling-bug/ describes a bug
which we also encountered on nagios 3.2 in lucid. After the clocks are
set back 1 hour for Daylight Saving Time (last weekend, in the UK),
nagios fails to schedule any service
Public bug reported:
Binary package hint: curl
Some HTTPS urls cause curl to fail with an "illegal parameter" error.
This error goes away if you manually specify "--sslv3"
e.g.
$ curl --version
curl 7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3
libidn/1.15
Protocols:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/23229572/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/23229573/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23229574/Dependencies.txt
** A
Public bug reported:
suspend appears to work but on resume the system says "Resume failure.
Press any key to continue" and the does a normal boot
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture: i386
DistroRelease:
