From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Question about integration of IPsec with SELinux?
Date: Mon, 13 Jun 2005 11:01:58 +0100 [thread overview]
Message-ID: <20050613100158.GA6610@lkcl.net> (raw)
In-Reply-To: <20050612233233.18232.qmail@web31610.mail.mud.yahoo.com>
On Sun, Jun 12, 2005 at 04:32:33PM -0700, Casey Schaufler wrote:
>
> --- Valdis.Kletnieks@vt.edu wrote:
>
>
> > You'll want *some* way of managing the allocation of
> > contexts cluster-wide,
> > just so you don't have two usages of jdoe_u that
> > refer to two different users..
>
> You will do well to consider the implications
> of allowing anything other than identical policies
> within a cluster or even a grid.
okay.
simplistic view: in nt-land, you have local workstations
'policy' and you have a global 'policy'.
the local workstations' policies are typically set up to
allow a local admin to log in to the machine, etc. using the
local SAM database (and you select the workstation domain /
local SAM by selecting the workstation's name on the login
dialog box to do that).
what you DO NOT DO is add any permissions into the local SAM database
for any local users to be able to access any of the domain resources.
in this way you have a scheme whereby the workstation is still
to some extent useable / recoverable even when disconnected
(isolated) from the domain.
do you _really_ want a domain-wide policy that specifies
"only the domain admin has the manage the network interfaces"?
because what happens if there _is_ no network by which you can access
or validate the domain policy such that you can trouble-shoot the
network interface?
!!!
even though it's access-control based, there is much to be
learned from the application of microsoft's nt domain protocol.
l.
--
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:[~2005-06-13 10:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 10:38 Question about integration of IPsec with SELinux? Park Lee
2005-06-11 17:27 ` Casey Schaufler
2005-06-11 18:45 ` Park Lee
2005-06-11 19:18 ` Valdis.Kletnieks
2005-06-11 19:49 ` Casey Schaufler
2005-06-12 2:16 ` Park Lee
2005-06-12 11:44 ` Luke Kenneth Casson Leighton
2005-06-12 12:39 ` Valdis.Kletnieks
2005-06-12 15:20 ` Luke Kenneth Casson Leighton
2005-06-12 19:18 ` Valdis.Kletnieks
2005-06-12 20:25 ` Luke Kenneth Casson Leighton
2005-06-12 20:30 ` Valdis.Kletnieks
2005-06-12 20:52 ` Luke Kenneth Casson Leighton
2005-06-12 21:45 ` Valdis.Kletnieks
2005-06-13 13:00 ` Stephen Smalley
2005-06-13 21:16 ` Luke Kenneth Casson Leighton
2005-06-14 13:21 ` Stephen Smalley
2005-06-14 14:31 ` Trent Jaeger
2005-06-15 22:04 ` Luke Kenneth Casson Leighton
2005-06-12 23:32 ` Casey Schaufler
2005-06-13 0:21 ` Valdis.Kletnieks
2005-06-13 10:01 ` Luke Kenneth Casson Leighton [this message]
2005-06-13 13:37 ` Valdis.Kletnieks
2005-06-13 14:10 ` Casey Schaufler
2005-06-13 12:49 ` Stephen Smalley
2005-06-13 21:17 ` Luke Kenneth Casson Leighton
2005-06-13 12:37 ` Stephen Smalley
2005-06-13 21:19 ` Luke Kenneth Casson Leighton
2005-06-12 12:34 ` Valdis.Kletnieks
2005-06-12 15:25 ` Luke Kenneth Casson Leighton
2005-06-12 16:16 ` Park Lee
2005-06-12 17:50 ` Casey Schaufler
2005-06-12 16:34 ` Park Lee
2005-06-12 17:02 ` Park Lee
2005-06-12 17:46 ` Casey Schaufler
[not found] <20050613213951.GB17617@lkcl.net>
2005-06-13 22:03 ` Casey Schaufler
2005-06-13 22:44 ` Luke Kenneth Casson Leighton
2005-06-16 16:01 ` Brian T. Sniffen
-- strict thread matches above, loose matches on Subject: below --
2005-06-14 18:11 Park Lee
2005-06-14 21:23 ` Casey Schaufler
2005-06-15 1:20 ` Park Lee
2005-06-15 3:00 ` Casey Schaufler
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=20050613100158.GA6610@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=casey@schaufler-ca.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.