This bug was fixed in the package nagios3 - 3.5.1.dfsg-2.1ubuntu7
---
nagios3 (3.5.1.dfsg-2.1ubuntu7) artful; urgency=medium
* SECURITY REGRESSION: event log cannot open log file (LP: #1690380)
- debian/patches/CVE-2016-9566-regression.patch: relax permissions on
log
This bug was fixed in the package nagios3 - 3.5.1-1ubuntu1.3
---
nagios3 (3.5.1-1ubuntu1.3) trusty-security; urgency=medium
* SECURITY REGRESSION: event log cannot open log file (LP: #1690380)
- debian/patches/CVE-2016-9566-regression.patch: relax permissions on
log files
This bug was fixed in the package nagios3 - 3.5.1.dfsg-2.1ubuntu3.3
---
nagios3 (3.5.1.dfsg-2.1ubuntu3.3) yakkety-security; urgency=medium
* SECURITY REGRESSION: event log cannot open log file (LP: #1690380)
- debian/patches/CVE-2016-9566-regression.patch: relax permissions on
This bug was fixed in the package nagios3 - 3.5.1.dfsg-2.1ubuntu1.3
---
nagios3 (3.5.1.dfsg-2.1ubuntu1.3) xenial-security; urgency=medium
* SECURITY REGRESSION: event log cannot open log file (LP: #1690380)
- debian/patches/CVE-2016-9566-regression.patch: relax permissions on
This bug was fixed in the package nagios3 - 3.5.1.dfsg-2.1ubuntu5.2
---
nagios3 (3.5.1.dfsg-2.1ubuntu5.2) zesty-security; urgency=medium
* SECURITY REGRESSION: event log cannot open log file (LP: #1690380)
- debian/patches/CVE-2016-9566-regression.patch: relax permissions on
Thanks for the test! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690380
Title:
"Cannot open log file '/var/log/nagios3/nagios.log' for reading" error
from nagios web UI when view alert
I can confirm that upgrading from 3.5.1.dfsg-2.1ubuntu1.1 to
3.5.1.dfsg-2.1ubuntu1.3 (from ppa:ubuntu-security-proposed/ppa) fixes
this issue on xenial.
Installing ppa:ubuntu-security-proposed/ppa's 3.5.1.dfsg-2.1ubuntu1.3 on
xenial without a previous nagios3 installed is OK too.
--
You
I have uploaded packages fixing this regression to the security team's
PPA here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
I'd appreciate it if someone could test them and verify they resolve the
issue for them.
I'll publish them as a security regression fix
** Also affects: nagios3 (Ubuntu Artful)
Importance: Undecided
Status: Triaged
** Also affects: nagios3 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nagios3 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: nagios3 (Ubuntu
That's right. I should have been more clear in my last comment (or have
stayed silent). I wanted to point out that while
3.5.1.dfsg-2.1ubuntu1.2's changelog claims to "Fix permissions", it's
fixing something entirely different to this issue.
--
You received this bug notification because you are
** Changed in: nagios3 (Ubuntu)
Status: Confirmed => Triaged
** Also affects: nagios3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nagios3 (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: nagios3 (Ubuntu)
Status: Confirmed => Triaged
** Also affects: nagios3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nagios3 (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Hi Jeremy,
I don't think there was any intention that this bug would be fixed by
that upload?
---
For reference, the upstream changes basically switched permissions to
0644 via:
https://github.com/NagiosEnterprises/nagioscore/commit/7af89e5886192dfbbb28317ed2e4883ee92e13e0
Hi Jeremy,
I don't think there was any intention that this bug would be fixed by
that upload?
---
For reference, the upstream changes basically switched permissions to
0644 via:
https://github.com/NagiosEnterprises/nagioscore/commit/7af89e5886192dfbbb28317ed2e4883ee92e13e0
Not fixed by this:
https://launchpad.net/ubuntu/+source/nagios3/3.5.1.dfsg-2.1ubuntu1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690380
Title:
"Cannot open log file
This describes how this was fixed in nagios 4.3.0 upstream:
https://github.com/NagiosEnterprises/nagioscore/issues/303#issuecomment-305149033
** Bug watch added: github.com/NagiosEnterprises/nagioscore/issues #303
https://github.com/NagiosEnterprises/nagioscore/issues/303
--
You received
If manually alter permissions (which isn't a persistent solution due to
log rotation):
sudo chmod go+r /var/log/nagios3/nagios.log
Then can see things like this:
[2017-05-15 14:31:10] Nagios 3.5.1 starting... (PID=2141)
...here:
http://localhost/cgi-
I can at leas confirm that I see the "fail to open" when just installing
and opening the history as outlined in the report - yet I never use
nagios so this might be normal (don't think so)?
For now setting to confirmed and let the security Team which knows what
was changed review.
** Changed in:
Subscribing ubuntu-security to evaluate if this is really a regression-
update bug due to CVEs.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690380
Title:
** Description changed:
Ubuntu 16.04.2 LTS
nagios3 and nagios3-cgi 3.5.1.dfsg-2.1ubuntu1.1
If install nagios3 package and then view Alert History, Notification
History or Events pages (and maybe others), e.g.:
http://localhost/cgi-bin/nagios3/history.cgi?host=localhost
- Then
20 matches
Mail list logo
