All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffry Smith <smith@missioncriticallinux.com>
To: selinux@tycho.nsa.gov, linux-privs-discuss@sourceforge.net
Subject: SELinux & Linux-privs projects
Date: Thu, 11 Jan 2001 09:44:54 -0500	[thread overview]
Message-ID: <E14GiyE-0000nL-00@smith> (raw)

Sent to both lists
Since I hadn't seen any traffic on the two lists about the other project, I 
thought I'd cross-send a message, to ensure the two communities are aware of 
what the other is doing.  I figure, although the projects are tackling 
different parts of the security of linux, there should be some overlap, since 
privileges should make it easier to do the type enforcement (I think), and the 
type enforcement can help with requirements for privileges (right?).

Comments?  

jeff


--
You have received this message because you are subscribed to the selinux 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:[~2001-01-11 14:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 14:44 Jeffry Smith [this message]
2001-01-11 15:20 ` SELinux & Linux-privs projects Stephen Smalley
2001-01-11 16:41   ` Huagang Xie
2001-01-11 16:46     ` [Linux-privs-discuss] " Christoph Hellwig
2001-01-11 15:45 ` [Linux-privs-discuss] " Christoph Hellwig
2001-01-11 16:04   ` Stephen Smalley
2001-01-11 16:16     ` Christoph Hellwig
2001-01-11 16:48       ` Stephen Smalley
2001-01-11 17:35         ` Casey Schaufler
2001-01-11 18:31           ` Stephen Smalley
2001-01-11 18:56             ` (offtopic) " Andrew Morgan
2001-01-11 18:59             ` Christoph Hellwig
2001-01-11 20:54               ` Stephen Smalley
2001-01-12  0:25             ` [Linux-privs-discuss] " Casey Schaufler
2001-01-11 16:59       ` Stephen Smalley
2001-01-23 16:13         ` Robert Watson
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23 17:44 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=E14GiyE-0000nL-00@smith \
    --to=smith@missioncriticallinux.com \
    --cc=linux-privs-discuss@sourceforge.net \
    --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.