From: Bennett Todd <bet@rahul.net>
To: Pedro Rosa <Pedro.Rosa@ksu.ru>
Cc: Kurth Bemis <kurth@usaexpress.net>, selinux@tycho.nsa.gov
Subject: Re: Secure?
Date: Fri, 16 Mar 2001 16:51:08 -0500 [thread overview]
Message-ID: <20010316165108.A12384@rahul.net> (raw)
In-Reply-To: <3AB1F827.3010308@ksu.ru>; from Pedro.Rosa@ksu.ru on Fri, Mar 16, 2001 at 02:25:27PM +0300
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
2001-03-16-06:25:27 Pedro Rosa:
> [...] the presence of WuFTP is probably the most questionable
> program in selinux. Not only in technical terms but also it arises
> questions in the concept itself.
I don't see that at all.
The concept of selinux, as it stands today, is (I believe --- if
people think I'm wrong please straighten me out:-) to experiment
with a novel model of mandatory access control, on a system which is
exceedingly wide-spread and getting more so rapidly, one which
stands a chance, in the reasonable future, of being usable in many,
perhaps most settings.
Today it's an early research project, and the specific focus is
on experimenting with the policy definition mechanism, and trying
to evolve a comfortable to manage, flexible, suitably high-level
setup for expressing policy decisions, while letting people get
comfortable with the performance, the stability, and the way the
resulting system behaves. The reasonable decision is to try to
integrate it into the most widely-used distribution, and to confine
the focus of this project to just the MAC features, patching other
components only as necessary to make them work.
Meanwhile, in unrelated developments, it's fair to hope that the
popular distributions may get more secure as time goes by; certainly
they're showing some interest in that area. I believe RH7.1 may be
the best Red Hat to date.
I'm expecting it'll be a year or two before this selinux thing will
be in a state of maturity and stability to become part of a major
distribution outright. Perhaps by then Red Hat will be shipping a
better-founded ftpd. I've rpmmed a port of the OpenBSD ftpd, it's
not particularly tricky to do so.
-Bennett
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-03-16 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 13:52 Secure? Kurth Bemis
2001-03-16 11:25 ` Secure? Pedro Rosa
2001-03-16 21:51 ` Bennett Todd [this message]
2001-04-07 5:49 ` Secure? Albert D. Cahalan
2001-03-16 16:03 ` Secure? Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 17:33 Secure? Ben Breuninger
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=20010316165108.A12384@rahul.net \
--to=bet@rahul.net \
--cc=Pedro.Rosa@ksu.ru \
--cc=kurth@usaexpress.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.