All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:44:54 +0100	[thread overview]
Message-ID: <20050613224454.GF17617@lkcl.net> (raw)
In-Reply-To: <20050613220328.31770.qmail@web31602.mail.mud.yahoo.com>

On Mon, Jun 13, 2005 at 03:03:28PM -0700, Casey Schaufler wrote:
> 
> 
> --- Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> 
> 
> >  wilma@DOI1 has **nothing** to do with wilma@DOI2.
> 
> This is the sort of thing that seperates the
> developers from the admins. Of course wilma@DOI1
> isn't wilma@DOI2. Nonetheless, reams of
> documentation and countless warnings
> notwithstanding, the human that creates the mapping
> between DOI1 and DOI2 will 99 44/100% of the time
> map wilma directly to wilma. It's bad enough for
> usernames. I see no reason to expect it to be
> any better for policy constructs.

 everyone sees "Administrator" on local workstations.

 do they _genuinely_ believe that "Administrator" on workstation
 1 is the same as "Administrator" on workstation 2??

 ... but anyway: the lessons there should be learned from the
 way that nt's "active directory" infrastructure is managed.

 if it's dumb enough for nt admins to not screw up...


--
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:[~2005-06-13 22:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050613213951.GB17617@lkcl.net>
2005-06-13 22:03 ` Question about integration of IPsec with SELinux? Casey Schaufler
2005-06-13 22:44   ` Luke Kenneth Casson Leighton [this message]
2005-06-16 16:01   ` Brian T. Sniffen
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
  -- strict thread matches above, loose matches on Subject: below --
2005-06-11 10:38 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
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

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=20050613224454.GF17617@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.