From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] logrotate: /var/log/portage/elog "insecure permissions"?
Date: Sun, 28 Aug 2011 12:14:11 +0100 [thread overview]
Message-ID: <201108281214.16339.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4E3EAD32.1060106@binarywings.net>
[-- Attachment #1: Type: Text/Plain, Size: 1775 bytes --]
On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote:
> Am 07.08.2011 02:22, schrieb Mick:
> > On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
> >> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> >>> 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. ;-)
> >>
> >> Yes that fixes it. The latest portage ebuilds include an updated config
> >> file.
> >
> > Hmm ... it still complains here!
> >
> > error: error setting owner of
> > /var/log/portage/elog/summary.log-20110801.gz: Operation not permitted
> >
> >
> > This is my /etc/logrotate.d/elog-save-summary:
> > ===================================
> > /var/log/portage/elog/summary.log {
> >
> > su portage portage
> >
> > missingok
> > nocreate
> > delaycompress
> >
> > }
> > ===================================
> >
> > # ls -la /var/log/portage/elog/summary.log
> > -rw-rw-r-- 1 root portage 4326 Aug 6 09:44
> > /var/log/portage/elog/summary.log
> >
> > Can you see anything amiss?
>
> At least on my system, /var/log/portage has the following permissions:
> drwxr-xr-x root root
>
> Only root can write, therefore the config must read
>
> /var/log/portage/elog/summary.log {
> su root portage
> missingok
> nocreate
> delaycompress
> }
The latest logrotate update wanted to change the above line from su root
portage to su portage portage ...
Should I be changing the ownership of /var/log/portage and /var/log/portage
elog?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-28 11:14 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
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 [this message]
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=201108281214.16339.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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