All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: antoine <antoine@nagafix.co.uk>
Cc: ivg2@cornell.edu, SELinux <selinux@tycho.nsa.gov>, walters@redhat.com
Subject: Re: mdadm policy
Date: Fri, 24 Jun 2005 23:42:10 -0400	[thread overview]
Message-ID: <42BCD292.3090103@redhat.com> (raw)
In-Reply-To: <1119641274.9645.58.camel@localhost>

antoine wrote:

>On Fri, 2005-06-24 at 15:05 -0400, Ivan Gyurdiev wrote:
>  
>
>>>So it looks to me like the transition to sendmail should always be
>>>included - well actually, ifdef(mta.te).
>>>      
>>>
>>cc-ed Dan Walsh.
>>Proposed transition to sendmail from mdadm.te
>>(so it can send alerts to user).
>>
>>Re: can_exec({ bin_t, sbin_t }) rule
>>
>>Antoine, you have to be root/sysadm_t to configure
>>execution of such programs, right? If you have sysadm_t, you
>>can disable any and all security. The only protection
>>from sysadm_t that selinux provides is protection from
>>inadvertently running hostile code that messes w/ selinux
>>files - that's why we have a role called secadm_t
>>(I think this is work in progress).
>>    
>>
>I admit the threat is minimal, but I just don't like the idea of running
>things as mdadm_t when it isn't necessary.
>You would need to know what is run by mdadm (as mdadm.conf is not
>readable by non root/sysadm_t) *and* find a flaw in it *and* trigger the
>mdadm error condition. Very slim indeed.
>On the other hand, any flaw in one of the bin_t/sbin_t programs run by
>mdadm would lead to a full compromise (using raw disks). And there has
>been more than one flaw found in sendmail/postfix/... And since it is
>avoidable, why not remove access to raw disks before launching the
>program. (I think the transition to sendmail_t is the minimum)
>
>  
>
>>So, we can't stop an intentional attack like this.
>>The only question is whether we should stop unintentional
>>attack (sysadm doesn't know bin_t/sbin_t program is hostile,
>>sysadm installed it anyway, sysadm doesn't have capability
>>to write to fixed_disk_device, but mdadm does, and 
>>gives hostile program desired escalation). 
>>    
>>
>Hostile program  *or* shell script with insecure privileges/files, etc.
>
>Antoine
>
>  
>
Add privmail attribute and you will transition to system_mail_t when 
starting sendmai.

-- 




--
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.

  parent reply	other threads:[~2005-06-25 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 23:27 mdadm policy antoine
2005-06-24  1:50 ` Ivan Gyurdiev
2005-06-24  9:35   ` antoine
2005-06-24 15:41     ` Ivan Gyurdiev
2005-06-24 15:58       ` Colin Walters
2005-06-24 16:35       ` antoine
2005-06-24 17:46         ` Ivan Gyurdiev
2005-06-24 18:02           ` antoine
2005-06-24 19:05             ` Ivan Gyurdiev
2005-06-24 19:27               ` antoine
2005-06-24 19:29                 ` Ivan Gyurdiev
2005-06-24 19:43                 ` Stephen Smalley
2005-06-25  3:42                 ` Daniel J Walsh [this message]
2005-06-24 19:47               ` Stephen Smalley
2005-06-24 11:29 ` Stephen Smalley

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=42BCD292.3090103@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=antoine@nagafix.co.uk \
    --cc=ivg2@cornell.edu \
    --cc=selinux@tycho.nsa.gov \
    --cc=walters@redhat.com \
    /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.