From: Jens Axboe <axboe@suse.de>
To: "Kristian Sørensen" <ks@cs.aau.dk>
Cc: umbrella-announce@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Umbrella-0.5.1 stable released
Date: Tue, 23 Nov 2004 16:14:35 +0100 [thread overview]
Message-ID: <20041123151435.GD13174@suse.de> (raw)
In-Reply-To: <200411231604.25522.ks@cs.aau.dk>
On Tue, Nov 23 2004, Kristian Sørensen wrote:
> On Tuesday 23 November 2004 15:48, Jens Axboe wrote:
> > On Tue, Nov 23 2004, Kristian Sørensen wrote:
> > > Hi all!
> > >
> > > We are pleased to inform you that Umbrella 0.5.1 is now released. This is
> > > a very stable release, which has been tested on our workstations for 6+
> > > days continously.
> > >
> > > Get the release here:
> > > http://prdownloads.sourceforge.net/umbrella/umbrella-0.5.1.tar.bz2?downlo
> > >ad
> > >
> > > The strategy of the further development of Umbrella is to have
> > > * STABLE and well tested Umbrella as patches
> > > * UNSTABLE bleeding edge technology in the CVS module umbrella-devel
> > >
> > >
> > > We have lots of new stuff and optimizations in the CVS, which slowley
> > > will be applied and tested before getting realeased as patches. Currently
> > > we have these in the CVS:
> > > * New, small and efficient bit vector
> > > * New datastructure for storing restrictions
> > > See this thread for details:
> > >
> > > http://sourceforge.net/mailarchive/forum.php?thread_id=5886152&forum_id=4
> > >2079 * Restrictions on process signaling
> > > * Authentication of binaries (still under development for the 0.6
> > > release)
> >
> > And umbrella is?
> Undskyld - vi plejer at tilføje en beskrivelse... her kommer den:
>
> Umbrella is a security mechanism which implements a combination of
> process-based Mandatory Access Control (MAC) and authentication of
> files through Digital Signed Binaries (DSB) for Linux based consumer
> electronics devices ranging from mobile phones to settop boxes.
>
> Umbrella is implemented on top of the Linux Security Modules (LSM)
> framework. The MAC scheme is enforced by a set of restrictions on
> each process. This policy is distributed with a binary in form of
> execute restrictions (in the file signature) and within the program,
> where the developer has the opportunity of making a "restricted fork"
> for setting restrictions for new children.
Thanks! Sometimes being lazy does pay off.
--
Jens Axboe
prev parent reply other threads:[~2004-11-23 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 14:44 Umbrella-0.5.1 stable released Kristian Sørensen
2004-11-23 14:48 ` Jens Axboe
2004-11-23 15:00 ` Simon Burke
2004-11-23 15:04 ` Kristian Sørensen
2004-11-23 15:14 ` Jens Axboe [this message]
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=20041123151435.GD13174@suse.de \
--to=axboe@suse.de \
--cc=ks@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=umbrella-announce@lists.sourceforge.net \
/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