From: Amon Ott <ao@rsbac.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] RSBAC 1.3.5 released
Date: Thu, 19 Jul 2007 11:37:01 +0200 [thread overview]
Message-ID: <200707191137.02048.ao@rsbac.org> (raw)
Hello everyone!
Rule Set Based Access Control (RSBAC) 1.3.5 has been released for both
Linux kernels 2.4.34.5 and 2.6.22.1.
You can download the new version from http://www.rsbac.org
RSBAC is one of the leading access control systems for the Linux
kernel with a good selection of access control models, see
http://www.rsbac.org/why for more details.
Important changes since 1.3.4:
* Fixes compilation errors with some configurations.
* Some safety measures with null pointers.
* Fixes an important bug with User Management password hashing,
introduced with newer 2.6 kernel crypto API.
Major improvements over the 1.2.x series:
Speed and scalability:
- Cache for inherited filesystem attribute values
- Automatically scaling hash tables for generic lists to minimize
list lookups
- Change network templates to handle up to 25 ip networks and up to
10 port ranges per template
- Various smaller optimizations
More control:
- Fine grained setuid control also in RC (type of the target user)
and ACL (acl at the target user) models
- UNIX sockets as new filesystem target type, thus more fine grained
control with RC types and ACLs
- Further improved IPC communication control
- RSBAC User Management password history with configurable length to
avoid password reuse.
- New request type AUTHENTICATE against USER targets. No
authentication against RSBAC UM without this right in RC and ACL, so
even harder to brute force attack
Amon.
--
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
reply other threads:[~2007-07-19 10:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200707191137.02048.ao@rsbac.org \
--to=ao@rsbac.org \
--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 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®