[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#701476: marked as done (unblock: nagios-nrpe/2.13-3)

Your message dated Sat, 09 Mar 2013 11:20:25 +0000
with message-id <1362828025.26434.9.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#701476: unblock: nagios-nrpe/2.13-2
has caused the Debian Bug report #701476,
regarding unblock: nagios-nrpe/2.13-3
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 owner@bugs.debian.org
immediately.)


-- 
701476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701476
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package nagios-nrpe.

The update is documentation only. It's done to address #547092: SSL support
is fundamentally broken in NRPE, which cannot be fixed easily (breaking
the protocol and hence compatibility with non-Debian npre hosts),

The update changes the documentation to warn against using the option. This
downgrades the bug to an important functionality problem, but not RC since
NRPE is usable securely without SSL in many cases.

unblock nagios-nrpe/2.13-2


Thanks,
Thijs

--- End Message ---
--- Begin Message --- 
On Sat, 2013-02-23 at 17:45 +0100, Alexander Wirt wrote:
> Thijs Kinkhorst schrieb am Saturday, den 23. February 2013:
> > Please unblock package nagios-nrpe.
> > 
> > The update is documentation only. It's done to address #547092: SSL support
> > is fundamentally broken in NRPE, which cannot be fixed easily (breaking
> > the protocol and hence compatibility with non-Debian npre hosts),
> > 
> > The update changes the documentation to warn against using the option. This
> > downgrades the bug to an important functionality problem, but not RC since
> > NRPE is usable securely without SSL in many cases.
[...]
> Hold on please :). We agreed on IRC earlier that morning to wait for the
> coming security update.

-3 unblocked.

fwiw:

++NOTE: the currently shipped native SSL support of NRPE is not an
++adequante protection, because it does not verify clients and

s/adequante/adequate/

Regards,

Adam

--- End Message ---
Reply to: