Planning v1.2.0

From: owner-rsbac@compuniverse.de [mailto:owner-rsbac@compuniverse.de]On
Subject: Planning v1.2.0
Date:

Next Article (by Subject): Planning v1.2.0 - update Amon Ott
Previous Article (by Subject): Planning v1.2.0 Amon Ott
Top of Thread: Planning v1.2.0 Amon Ott
Articles sorted by: [Date] [Author] [Subject]

I don't see any reason why RSBAC should care about libc and stack/heap since
it is already taken care about by other projects. Many people for example
use PaX (which is included in grsecurity) and having stack and heap things
in RSBAC would just lead to conflict.


- Jörg Lübbert

-----Original Message-----
From: owner-rsbac@compuniverse.de [mailto:owner-rsbac@compuniverse.de]On
Behalf Of Amon Ott
Sent: Wednesday, July 11, 2001 11:58 AM
To: RSBAC List
Subject: Planning v1.2.0


Hi folks!

1.1.2 is meant as the last 1.1.x version to come out. If 1.1.3 comes, it
will
not bring major functional changes, but rather important bugfixes.

For 1.2.0, there are currently planned:

- Move most lists to generic lists, possibly splitting them up for
different models. This will break on-disk compatibility and auto-update, but
a
backup-restore will work.

- Real network access control as descibed in previous mails, with
socket-template and socket objects

- PM module overhaul, PM administration menues

- (maybe) Optional filesystem object redirection support, e.g. to provide
separate /tmp dirs for all users. There might be a separate module just
doing
redirection. There are many problems involved with this.

- Port to Linux Security Module (LSM) generic kernel interception
interface, likely to be included into 2.5 kernel series.

- (maybe) RC roles time limits

Please comment and add your own wishlist to be discussed.

Amon.
-
To unsubscribe from the rsbac list, send a mail to
majordomo@rsbac.org with
unsubscribe rsbac
as single line in the body.

-
To unsubscribe from the rsbac list, send a mail to
majordomo@rsbac.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.