The stock not security reply can be found at
https://wiki.ubuntu.com/SecurityTeam/BugTriage#Not_Security which says
"unmarked it as a security issue since this bug does not show evidence
of allowing attackers to cross privilege boundaries nor directly cause
loss of data/privacy."
--
You received
I checked on IRC #ubuntu-hardened (the actual name for the #ubuntu-
security channel) and was told that "we typically only consider bugs to
have a security impact if there's an attacker to the story". The reason
for that is "else, almost every bug has an indirect security impact"
which I can see
That does sound a bit tenuous but could be easily settled by a policy decision
on whether:
i) Bugs that directly block the installation of security patches are security
bugs.
ii) Bugs that cause disk space to fill which in turn block security patch
install are security bugs.
I would
I'll just point out that this can perhaps be considered a security bug,
because if log rotations stop happening, the disk will inevitably fill
up sooner or later, which means security patches will stop being
applied, which means the machine will become insecure. You might say
that that is a bit
Hi,
the fix is upstream released in logwatch 3.11 but we are post freeze for zesty.
We will almost for sure pick that up in zesty+1.
The question now is for the SRU work to at least Trusty and Xenial.
The upstream fix [1] is not super-small and I haven't checked yet how cleanly
that would apply
Still present on 14.04.1. I am seeing this again today.
I wonder if this would count as a papercut? I am not really sure as
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Mission says "Have the
impression the desktop is rock solid." and this is a log rotation system
that only moans if root
** Changed in: logrotate (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
Logrotate fails repeatedly with /etc/cron.daily/logrotate:
** Changed in: logrotate (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
I am also seing this on a 14.04 server using logrotate package version
3.8.7-1ubuntu1:
$ dpkg -l|grep logrotate
ii logrotate 3.8.7-1ubuntu1
amd64Log rotation utility
$ lsb_release -a
No LSB modules are available.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logrotate (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
** Changed in: logrotate (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
11 matches
Mail list logo
