roger munk wrote:
> On Thu, Jan 29, 2009 at 1:13 AM, Brian Rectanus
> <Brian.Rectanus@...> wrote:
>>> I can access the console via openssl, so I think the problem is with
>>> libcurl. Any ideas which Debian package works with mlogc?
>> Verify that mlogc uses https in the URI and that the console is indeed
>> running SSL on that port.
> Hey Brian,
> Thanks, I verified that mlogc uses HTTPS in the URI and was able to
> connect to the console using the openssl. The console is running on a
> WinXP box, if that matters. I noticed that I can connect to the
> console using openssl via sslv3 but not sslv2. Could mlogc be trying
> to connect via sslv2? Is that a configurable parameter?
> - Roger
It is a handshake problem, but not sslv2 related (at leat the error is
an sslv3 error). This was a problem a while back with using gnutls (vs
openssl). Verify that you are not using that version of curl.
Here is the thread on that one:
There was a workaround in editing the mlogc source - try that if still
having issues. If that does not fix it, then I'll take a closer look.