From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] logrotate: /var/log/portage/elog "insecure permissions"?
Date: Fri, 05 Aug 2011 17:59:00 +0200 [thread overview]
Message-ID: <4E3C1344.5010903@binarywings.net> (raw)
In-Reply-To: <4E3C0AD2.6080409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Am 05.08.2011 17:22, schrieb Jarry:
> Hi,
> today I received this mail from cron:
> ---
> error: skipping "/var/log/portage/elog/summary.log" because
> parent directory has insecure permissions (It's world writable
> or writable by group which is not "root") Set "su" directive
> in config file to tell logrotate which user/group should be
> used for rotation.
> ---
>
> My /var/log/portage/elog has this permissions:
> drwxrws--- 2 portage portage 4096 Jun 1 2010 elog
>
> What is wrong with it? I'm pretty sure I did not touch it
> for years so I'm surprised logrotate is suddenly complaining
> (it has been updated recently, that might be reason).
>
> Anyway, how should those permissions look like to make
> logrotate (and cron) happy?
>
> Jarry
>
Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
your config to look like this:
/var/log/portage/elog/summary.log {
su portage portage
...
}
Disclaimer: I've not really tried this (yet) but I think I'm able to
read changelogs and man-pages. ;-)
[1] https://bugzilla.redhat.com/show_bug.cgi?id=680799
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-05 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 15:22 [gentoo-user] logrotate: /var/log/portage/elog "insecure permissions"? Jarry
2011-08-05 15:59 ` Florian Philipp [this message]
2011-08-05 22:08 ` Neil Bothwick
2011-08-07 0:22 ` Mick
2011-08-07 15:20 ` Florian Philipp
2011-08-09 20:13 ` Mick
2011-08-28 11:14 ` Mick
2011-08-28 18:44 ` Florian Philipp
2011-08-29 13:42 ` Florian Philipp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3C1344.5010903@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox