All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Erich Schubert <erich@debian.org>
Cc: selinux@tycho.nsa.gov, bam@snoopy.apana.org.au
Subject: Re: SELinux Policy patches
Date: Tue, 20 Jul 2004 15:25:10 +1000	[thread overview]
Message-ID: <200407201525.10272.russell@coker.com.au> (raw)
In-Reply-To: <20040719143857.GD13205@wintermute.xmldesign.de>

On Tue, 20 Jul 2004 00:38, Erich Schubert <erich@debian.org> wrote:
> Hi,
>
> > > # I also added (don't remember what that was needed for):
> > > can_exec(logrotate_t, logrotate_exec_t)
> >
> > Can you find out what it is needed for?
>
> For executing /usr/bin/savelog:
>
> denied  { execute_no_trans } for  pid=21289 exe=/bin/dash
> path=/usr/bin/savelog dev=sda3 ino=299540
> scontext=system_u:system_r:logrotate_t
> tcontext=system_u:object_r:logrotate_exec_t tclass=file

OK, I've added that to my tree.

> I do have some weird behaviour with logrotate OR logcheck on this box:
>
> denied  { search } for  pid=21251 exe=/usr/sbin/logrotate name=selinux
> dev=sda3 ino=274182 scontext=system_u:system_r:logrotate_t
> tcontext=system_u:object_r:selinux_config_t tclass=dir

I think that we can dontaudit that one, that would be from SE Linux library 
calls.

> denied  { search } for  pid=21251 exe=/usr/sbin/logrotate name=root
> dev=sda3 ino=318865 scontext=system_u:system_r:logrotate_t
> tcontext=root:object_r:staff_home_dir_t tclass=dir
>
> Seems like some logrotate cron job is doing a "find"?

As discussed on IRC that would be from cron setting the current directory to 
the home directory.

> Also i do get this error message frequently:
>
> denied  { relabelfrom } for  pid=4768 exe=/bin/cp name=checked dev=md0
> ino=160726 scontext=system_u:system_r:logrotate_t
> tcontext=system_u:object_r:logrotate_tmp_t tclass=file
> denied  { relabelto } for  pid=4768 exe=/bin/cp name=checked dev=md0
> ino=160726 scontext=system_u:system_r:logrotate_t
> tcontext=system_u:object_r:logrotate_tmp_t tclass=file
>
> What is happening here?

That's a bug in cp.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2004-07-20 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16  0:22 SELinux Policy patches Erich Schubert
2004-07-16  2:34 ` Russell Coker
2004-07-16  8:19   ` Luke Kenneth Casson Leighton
2004-07-16  8:43     ` Russell Coker
2004-07-16 10:55     ` Luke Kenneth Casson Leighton
2004-07-16 11:28       ` Russell Coker
2004-07-16 11:48   ` Erich Schubert
2004-07-19 14:38   ` Erich Schubert
2004-07-20  5:25     ` Russell Coker [this message]
2004-07-16 11:57 ` Erich Schubert
2004-07-16 15:13   ` Stephen Smalley
2004-07-16 21:23   ` Russell Coker

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=200407201525.10272.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=bam@snoopy.apana.org.au \
    --cc=erich@debian.org \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.