Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 858422 - app-admin/logrotate does complain about world readable lock even if it is not
Summary: app-admin/logrotate does complain about world readable lock even if it is not
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2022-07-16 17:28 UTC by Klaus Ethgen
Modified: 2022-07-19 04:13 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Ethgen 2022-07-16 17:28:12 UTC
I get the following error message:
warning: state file /var/lib/misc/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition...

This is fully bullshit for two reasons:
1. `ls /var/lib/misc/logrotate.status` gives:
~> ll /var/lib/misc/logrotate.status
-rw-r----- 1 root root 1,2K 16. Jul 16:45 /var/lib/misc/logrotate.status

So the file is neither world readable nor by any user.

2. Even if it is setup that way, it is fully choice of root to do so. He has full control over the config files of logrotate (if he has not, he would have much bigger problems!)

Reproducible: Always

Steps to Reproduce:
1. run logrotate
Actual Results:  
It spams about a not world readable world readable file

Expected Results:  
It would work without complaining
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-07-16 17:30:09 UTC
Please be more polite instead of talking about "bullshit".

Does the warning occur more than once? At least in bug 847382, the discussion (and my experience) seemed to conclude that it was a one-off warning at most.
Comment 2 Klaus Ethgen 2022-07-17 06:07:56 UTC
Well, I got it multiple times and I remember the last time that I was already pissed about the … message.

I take security and messages about it very serious. It cost me many times to get to the root of such messages. If is comes out to be … (sorry, I don't know any other word than that I already used), I am really pissed. And I only take the burden to open a bug if it comes again.

The system is a laptop where logrotate is not running regular.
Comment 3 Kamil Dudka 2022-07-18 07:28:09 UTC
I am afraid the steps to reproduce are too vague to take any action on this.  Please provide the output of two runs of `logrotate -v ...` on a single state file.