This bug was fixed in the package cups - 1.7.1-3
---
cups (1.7.1-3) unstable; urgency=low
[ Till Kamppeter ]
* Split binary package cups into cups and cups-core-drivers. In
low-footprint (mobile) environments we can restrict the printer
support to only IPP printers with
Thanks Didier, looks fine!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1268011
Title:
Inconsistent ownership/permissions of error_log in CUPS
Status in “cups” package in Ubuntu:
I noticed a problem in my patch: it is useless. :-) From the reporter:
At the same time, CUPS itself sets its log files by default to 644.
This is wrong; debian/rules sets LogFilePerm to 0640 through the
--with-log-file-perm=0640 configure argument. It has been this way
since cups 1.3.8-6 to fix
Log files which can potentially contain sensitive data should usually be
system_user:adm 640; the group adm purpose is that members can read
system log files. For harmless log files they can be root:root (or
from a system user if the daemon is not running as root) and 644.
It would be good if
This all is not new. From the git history, LP: #345953 got fixed by
the inclusion of the current (and mostly unchanged) of the
logfiles_adm_readable.dpatch by Martin for 1.3.9-16. The logrotate
script exists at least since cups 1.2. It has enforced 640 root lp
since 1.3.8-1.
That said, I open
The attachment 0001-Consolidate-logfiles-modes-and-groups-to-
be-0640-and.patch seems to be a patch. If it isn't, please remove the
patch flag from the attachment, remove the patch tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
OdyX, thanks for the patch, it looks OK for me. Please go ahead and
apply it to the next Debian package. Ubuntu will pick it up by auto-
syncing then.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Maybe you could avoid creating an empty file at all, or enforcing any
permissions on it? (logrotate would copy previous permissions by
default). From admin's point of view, it is cumbersome to adjust log
files permissions in two places: cups-files.conf and logrotate for CUPS.
--
You received
OdyX, pitti, I have never modified the ownership policy of CUPS' log
files. So I do not know which is the intended one root:adm?
root:lpadmin? 640? 644? What is the intended policy and what is its
rationale?
--
You received this bug notification because you are a member of Desktop
Packages,
9 matches
Mail list logo
