Your message dated Mon, 27 Oct 2008 23:58:27 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#503311: monit: Client Certificate authentication fails
with openssl-engine error
has caused the Debian Bug report #503311,
regarding monit: Client Certificate authentication fails with openssl-engine
error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
503311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503311
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: monit
Version: 1:4.10.1-4
Severity: grave
Justification: renders package unusable
After having upgraded to lenny, the monit webinterface no longer works with
client certificate authentication.
While using Debian Etch, with the exact same configuration it worked fine.
Here is the error logged by monit when trying to connect:
monit[2067]: monit: The client did not supply a required client certificate!
monit[2067]: monit: Openssl engine error: error:140D9115:SSL
routines:func(217):reason(277)
monit[2067]: monit: The client did not supply a required client certificate!
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (650, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26.7 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages monit depends on:
ii libc6 2.7-14 GNU C Library: Shared libraries
ii libssl0.9.8 0.9.8g-13 SSL shared libraries
monit recommends no packages.
monit suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Georges Toth wrote:
> Stefan Alfredsson wrote:
>> Was the client also upgraded in the process? Could it be a client
>> problem?
>> Does client certs still work with other servers?
>>
> You were right ... it was actually a client error.
> I recently upgraded to kde4, and since the ssl implementation in
> konqueror is kind of broken, I started using firefox.
> So with firefox the monit webinterface stopped working....and it still
> doesn't work with the etch version of monit.
>
> But using konqueror-3.5 it _does_ work. So it obviously is a client error.
> I am running gentoo on the client, so this may also apply to debian but
> may as well not.
>
> Sorry for the wrong report, and thanks for your time.
Sure, no problem! Closing this report.
Regards,
Stefan
--- End Message ---
