All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Bosko Radivojevic <bole@etf.bg.ac.yu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Security Protection System
Date: Fri, 18 Oct 2002 14:47:59 +0200	[thread overview]
Message-ID: <20021018124759.GF7875@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0210161607590.28724-100000@falcon.etf.bg.ac.yu>

On Wed, Oct 16, 2002 at 04:08:54PM +0200, Bosko Radivojevic wrote:
> LinSec team is proud to announce first stable release of LinSec.
> 
> LinSec, as the name says, is Linux Security Protection System. The main aim
> of LinSec is to introduce Mandatory Access Control (MAC) mechanism into
> Linux (as opposed to existing Discretionary Access Control mechanism).
> LinSec model is based on:
> 
>     * Capabilities
>     * Filesystem Access Domains
>     * IP Labeling Lists
>     * Socket Access Control

Can you describe, shortly, how LinSec is different from SELinux ?

I didn't see a FAQ on your web site.

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2002-10-18 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 13:28 2.5.43 hangs silently on boot Robinson Maureira Castillo
2002-10-16 14:08 ` Linux Security Protection System Bosko Radivojevic
2002-10-18 12:47   ` Jakob Oestergaard [this message]
2002-10-20 14:14   ` Pavel Machek

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=20021018124759.GF7875@unthought.net \
    --to=jakob@unthought.net \
    --cc=bole@etf.bg.ac.yu \
    --cc=linux-kernel@vger.kernel.org \
    /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.