In fact I have no idea why this is distributed to the distros instead of
reporting it to upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677501
Title:
no SSL certificate verify
To manage n
This has been fixed in 1.9.0-1.
** Changed in: icinga (Ubuntu)
Status: New => Fix Released
** Changed in: icinga (Ubuntu)
Assignee: (unassigned) => Alexander Wirt (formorer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Every nagios related component is configured to run as nagios:nagios, in
that way running them on Nagios and Icinga is possible without much
problems and we don't have to adapt any documentation for complicated
setup steps. Just changing the user for icinga isn't enough, there have
to be several ch
JTFR I (the debian Maintainer) will never support changing the user
icinga is running under. Any patch will therefore be ubuntu specfic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186550
Title:
sure, or you can use LDAP, *SQL or whatever for auth - but there is no
sensible default.
--
Integrate nagios users with system ones
https://bugs.launchpad.net/bugs/562146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Speaking with my nagios3 maintainer in debian hat on
> Why www-data would have to read shadow file?
> What about using pam modules?
even libpam needs access to the password hashes. Just by using libpam you don't
get magically access to them.
Citing from libapache2-mod-auth-pam package:
To use
