From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul.moore@hp.com>, Joy Latten <latten@austin.ibm.com>
Cc: cpebenito@tresys.com, redhat-lspp@redhat.com,
jbrindle@tresys.com, selinux@tycho.nsa.gov
Subject: Re: [redhat-lspp] labeled ipsec policy
Date: Mon, 20 Nov 2006 08:34:09 -0800 (PST) [thread overview]
Message-ID: <20061120163410.12804.qmail@web36611.mail.mud.yahoo.com> (raw)
In-Reply-To: <200611201124.19292.paul.moore@hp.com>
--- Paul Moore <paul.moore@hp.com> wrote:
> Hmmm, I suspect this will probably be a problem as
> the IPsec management tools
> serve a dual purpose, they control the IPsec
> configuration (sysadm_r) as well
> as the policy relating to labeling SAs (secadm_r).
> I guess we'll just have
> to settle for sysadm_r and deal with the fact that
> sysadm_r is going to have
> some control over the system's security policy in
> this case.
Alternatively, you might consider a separate
network security administrator role that is
associated with those tools. It might be better
than giving sysadm_r the additional responsibility.
Casey Schaufler
casey@schaufler-ca.com
--
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.
next prev parent reply other threads:[~2006-11-20 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 22:30 labeled ipsec policy Joy Latten
[not found] ` <200611201000.06118.pcmoore@engin.umich.edu>
2006-11-20 15:09 ` [redhat-lspp] " Joy Latten
2006-11-20 16:24 ` Paul Moore
2006-11-20 16:34 ` Casey Schaufler [this message]
2006-11-21 14:10 ` Christopher J. PeBenito
2006-11-27 20:51 ` [redhat-lspp] " Joy Latten
2006-11-29 14:59 ` Christopher J. PeBenito
2006-11-29 20:42 ` Venkat Yekkirala
2006-11-29 23:51 ` Joy Latten
2006-11-30 15:57 ` Venkat Yekkirala
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=20061120163410.12804.qmail@web36611.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=cpebenito@tresys.com \
--cc=jbrindle@tresys.com \
--cc=latten@austin.ibm.com \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@redhat.com \
--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.