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 to fixing this. I agree with mode 0640 but my only doubt is whether the group 'adm' is okay, rather than lpadmin. Users are not necessarily in both groups; therefore "adm" is the generic solution but could potentially forbid "lpadmin" users logfiles access (which, at a second thought, is probably fine). Therefore: * cups should be creating the logfiles 640 root:adm * logrotate should only let them be recreated that way too. Opinions about the attached patch? Cheers, OdyX ** Patch added: "0001-Consolidate-logfiles-modes-and-groups-to-be-0640-and.patch" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1268011/+attachment/3946225/+files/0001-Consolidate-logfiles-modes-and-groups-to-be-0640-and.patch -- 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: New Bug description: Package CUPS 1.7.1 in Ubuntu has a patch that changes ownership of all log files to root:adm. At the same time, cups-daemon.logrotate changes ownership to root:lpadmin, permissions 640 daily. At the same time, CUPS itself sets its log files by default to 644. Please make it a bit more consistent by default? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1268011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
