All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanel Kokk <tanel.kokk@seb.ee>
To: SELinux@tycho.nsa.gov
Subject: Re: Sendmail & SELinux policies
Date: Thu, 06 Apr 2006 14:49:44 +0300	[thread overview]
Message-ID: <44350058.7080505@seb.ee> (raw)
In-Reply-To: <1144323640.6176.5.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2006-04-06 at 12:09 +0300, Tanel Kokk wrote:

> This looks suspect, as the null device should be labeled null_device_t,
> not just device_t.  ls -Z /dev/null

Ouch! I have to note, that I have chrooted sendmail environment and 
/sm_chroot/dev/null really has a label device_t. Now fixed to null_device_t.

> 
>> audit2allow get:
>> allow sendmail_t device_t:chr_file { getattr ioctl };
>>
>> However I have this line in ./src/policy/domains/program/local.te:
>> allow sendmail_t device_t:chr_file { read write getattr ioctl };
>>
>> As I understand I already have allowing policy record for this 
>> situation. Why I still got this denied messages for sendmail_t?
> 
> First, I don't think you want to allow it (potential access to device
> nodes that don't have a specific type).  You want to fix the label
> on /dev/null instead.

OK. I'll check my dev files and fix them to appropriate label.

> Not sure why your local rule isn't applied though, unless you just
> didn't do a make load after adding it.  You can try doing a make clean
> load to be sure it was rebuilt.
> 

I allways did 'make relabel' and 'make reload'.

Thanks! I'll look things over.


-- 
Tanel Kokk


--
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:[~2006-04-06 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06  9:09 Sendmail & SELinux policies Tanel Kokk
2006-04-06 11:40 ` Stephen Smalley
2006-04-06 11:49   ` Tanel Kokk [this message]
2006-04-06 12:14     ` Stephen Smalley
2006-04-06 12:23       ` Tanel Kokk

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=44350058.7080505@seb.ee \
    --to=tanel.kokk@seb.ee \
    --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.