All of lore.kernel.org
 help / color / mirror / Atom feed
From: "richard offer" <offer@sgi.com>
To: selinux@tycho.nsa.gov
Subject: Re: [selinux] Re: Mirror Site
Date: Tue, 26 Dec 2000 16:23:44 -0800	[thread overview]
Message-ID: <1001226162345.ZM39431@sgi.com> (raw)
In-Reply-To: Magosányi Árpád <mag@bunuel.tii.matav.hu>        "Re: [selinux] Re: Mirror Site" (Dec 27, 12:11am)


* $ from mag@bunuel.tii.matav.hu at "27-Dec:12:11am" | sed "1,$s/^/* /"
*
*
* > Although the tools provided by Sourceforge are nice, we're hopeful that
* > the capabilities of our website, and the interaction provided by this
* > list will meet the needs of anyone who wants to work with the code.
* > If, as things progress, anyone believes that more support
* > infrastructure is required, please let us know.  We'll reexamine our
* > options if and when more is needed.
* >
*
* Having a project sourceforged is important not for just technical reasons.
* If the project is on sourceforge, it more likely attracts more developers
* and users, so the critical mass of the project is more easily reached.
* BTW, is there any official word (either from Linus or from NSA), when will
* flask integrated into the mainstream kernel sources? It is also a major
* issue from the "marketing" perspective. (I would be happy to see it in 2.5)

The continued addition of embryonic features to linux is what has kept 2.4 from
being released. This code has only been out for 2 days and is a research
project prototype at that, and we are already talking about adding it to the
main line ?


[ from the overview ]

  This work is not intended as a complete security solution for Linux.
  ...
  Instead, it is simply an example of how mandatory access controls that can
                           *******
  confine the actions of any process,
  including a superuser process, can be added into Linux. The focus of this
  work has not been on system assurance or other security features such
  as security auditing, although these elements are also important for a
  secure system.

Robert Watson (on the TrustedBSD list) says it best.

  Figuring out how the SELinux implementation fits into the bigger picture will
  be important -- it represents a large step forward in terms of the
  availability of secure open source operating systems.


This is good, interesting code, but that doesn't mean its ready for prime time
distribution yet.


I must be old, I'm getting too conservative....

richard.


-----------------------------------------------------------------------
Richard Offer          Widget FAQ --> http://reality.sgi.com/widgetFAQ/
{X,Motif,Trust} on {Irix,Linux}
__________________________________________http://reality.sgi.com/offer/

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.

  parent reply	other threads:[~2000-12-27  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-26 21:48 Mirror Site Howard D. Holm
2000-12-26 22:56 ` Ben Johnson
2000-12-26 23:11 ` [selinux] " Magosányi Árpád
2000-12-26 23:49   ` Andi Kleen
2000-12-27  0:46     ` sightly offtopic: mainstream Magosányi Árpád
2000-12-27  0:23   ` richard offer [this message]
2000-12-26 23:35 ` Mirror Site Grant Bayley
2000-12-30 19:34 ` RJ Atkinson

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=1001226162345.ZM39431@sgi.com \
    --to=offer@sgi.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.