mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: linux-kernel@vger.rutgers.edu
Cc: hlm@aplcore.jhuapl.edu
Subject: Re: Linux login security approaches
Date: Sat, 12 Dec 1998 01:40:29 -0500 (EST)	[thread overview]
Message-ID: <199812120640.BAA15964@saturn.cs.uml.edu> (raw)


H. L. Miller writes:

> On another question (more "on topic", perhaps), has anyone
> attempted or thought about attempting to add classification
> labels and mandatory access control extensions to Linux?

This being Linux, would you like the patch against 2.1.131?

> Since that is a continuing DoD requirement, which continues
> to be an unsatisfied requirement because there is no
> mainstream OS with those features, this would appear to be
> a window of opportunity for Linux.

Mailing list:
    Send to majordomo@morpork.shnet.org (or rsbac-request@)
    a message with a body of:    subscribe rsbac

Status:
    should be stable enough for real usage

Author:
    A. Ott

Web page:
    http://agn-www.informatik.uni-hamburg.de/people/1ott/rsbac/eng.htm

Goal:
    Orange Book (TCSEC) B1 level



Now, who wants to find all the covert channels?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~1998-12-12 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-12  6:40 Albert D. Cahalan [this message]
     [not found] <19981207144143.A19454@knt.terra.vein.hu>
     [not found] ` <Pine.LNX.4.05.9812080125180.3246-100000@cyril.iaeste.dtu.dk>
     [not found]   ` <19981209203129.C26554@pinguin.conetix.de>
     [not found]     ` <19981212061305.G386@uni-koblenz.de>
1998-12-13 15:25       ` jens

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=199812120640.BAA15964@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=hlm@aplcore.jhuapl.edu \
    --cc=linux-kernel@vger.rutgers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®