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: ivg2@cornell.edu, SELinux@tycho.nsa.gov
Subject: Re: dumb newbie questions
Date: Sun, 19 Jun 2005 23:10:36 +0100	[thread overview]
Message-ID: <20050619221035.GG8415@lkcl.net> (raw)
In-Reply-To: <20050619213151.53651.qmail@web31601.mail.mud.yahoo.com>

On Sun, Jun 19, 2005 at 02:31:51PM -0700, Casey Schaufler wrote:
 
> Yes, he has. I hope that effort is successful.
> I strongly dislike the direction of RedHat
> shipping a binary only policy, and one that
> so few people understand, and that the
> applications it impacts can't even be repaired
> by their maintainers. 

 as the bun-fight over crond demonstrated (at least to me), the
 maintainers _can_ listen - if you have enough time, patience and
 flexibility.

 for those people who missed it, crond (not the vixie cron, the other
 one) did not properly support selinux, and needed it.

 a long _long_ time was spent explaining to the maintainer of crond
 that yes, selinux really _does_ have a concept of "system".

 the poor guy had added the concept of "*system*" to cater
 for the fact that unix-on-its-own doesn't have a clue about
 "system" privileges, and he had added some extra field
 into his internal data structures in order to be able to
 distinguish between "system" level cron jobs [run as root]
 and those that were explicitly to be run under the username
 of "root".

 after about 10-15 email exchanges, he eventually explained
 things clearly enough for it to get through our thick heads,
 and _then_ we had enough of an understanding of what he had
 created, in order to be able to successfully convince him that
 yes, selinux's "system_u" needs to ride "on the back of" his
 pseudo-created "*system*" concept.
 
 from there i kind of lost the plot a bit (i overdid it a
 bit :) and he and dan managed to finish it off and write an
 acceptable patch.

 i put it to you, therefore, casey, that it is _your_ job - and mine -
 to explain selinux clearly enough, to be patient enough, to listen
 enough.

 the one about openssh (the file handle one where an exec()
 had happened and the file handle hadn't been closed) was _way_
 over my head, but heck - there were people here who understood it.

 one step at a time.

 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.

  reply	other threads:[~2005-06-19 22:10 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17 20:01 SELinux Integrated Logging Tool Brandon Pollet
2005-06-17 23:43 ` James Morris
2005-06-18 15:39 ` Steve G
2005-06-18 23:38   ` dumb newbie questions R. Steven Rainwater
2005-06-19  6:45     ` Ivan Gyurdiev
2005-06-19 16:40       ` Casey Schaufler
2005-06-19 19:51         ` Ivan Gyurdiev
2005-06-19 20:14           ` Casey Schaufler
2005-06-19 20:57             ` Ivan Gyurdiev
2005-06-19 21:31               ` Casey Schaufler
2005-06-19 22:10                 ` Luke Kenneth Casson Leighton [this message]
2005-06-20  0:28                   ` Casey Schaufler
2005-06-19 22:13             ` Luke Kenneth Casson Leighton
2005-06-20  0:16               ` Casey Schaufler
2005-06-20 19:21                 ` Luke Kenneth Casson Leighton
2005-06-20 20:41                   ` Casey Schaufler
2005-06-20 21:01                     ` Valdis.Kletnieks
2005-06-20 21:36                       ` Casey Schaufler
2005-06-22  9:48                         ` Christopher Warner
2005-06-19 20:41           ` Ivan Gyurdiev
2005-06-20  3:34             ` R. Steven Rainwater
2005-06-20  4:45               ` Valdis.Kletnieks
2005-06-20 14:45                 ` R. Steven Rainwater
2005-06-20 15:14                   ` Ivan Gyurdiev
2005-06-20 15:29                     ` R. Steven Rainwater
2005-06-20 15:44                       ` Ivan Gyurdiev
2005-06-20 16:40                         ` R. Steven Rainwater
2005-06-20 16:59                           ` Ivan Gyurdiev
2005-06-20 17:35                             ` Karl MacMillan
2005-06-20 18:06                             ` R. Steven Rainwater
2005-06-20 18:18                               ` Daniel J Walsh
2005-06-24  6:22                                 ` Russell Coker
2005-06-20 18:06                             ` Daniel J Walsh
2005-06-20 18:57                           ` Luke Kenneth Casson Leighton
2005-06-20 15:56                       ` Stephen Smalley
2005-06-20 19:05                       ` Luke Kenneth Casson Leighton
2005-06-20 16:28                     ` Stephen Smalley
2005-06-20 18:49               ` Luke Kenneth Casson Leighton
2005-06-19 22:17           ` Luke Kenneth Casson Leighton
2005-06-20  4:11             ` Ivan Gyurdiev
2005-06-20 13:12     ` Trevor Vaughan
2005-06-20 15:21       ` R. Steven Rainwater
2005-06-20 15:40         ` Ivan Gyurdiev
2005-06-20 16:20         ` Stephen Smalley
2005-06-30 22:11     ` cgiemail and senmail policy R. Steven Rainwater
2005-07-03 14:21       ` Daniel J Walsh

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=20050619221035.GG8415@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=casey@schaufler-ca.com \
    --cc=ivg2@cornell.edu \
    /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.