From: Chris Wright <chris@wirex.com>
To: linux-security-module@wirex.com
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] 2.5.35-lsm1
Date: Tue, 17 Sep 2002 12:57:20 -0700 [thread overview]
Message-ID: <20020917125720.K1972@figure1.int.wirex.com> (raw)
The Linux Security Modules project provides a lightweight, general
purpose framework for access control. The LSM interface enables
security policies to be developed as loadable kernel modules.
See http://lsm.immunix.org for more information.
2.5.35-lsm1 patch released. This is a rebase up to 2.5.35 as well as
numerous module updates and bugfixes.
Full lsm-2.5 patch (LSM + all modules) is available at:
http://lsm.immunix.org/patches/2.5/2.5.35/patch-2.5.35-lsm1.gz
The whole ChangeLog for this release is at:
http://lsm.immunix.org/patches/2.5/2.5.35/ChangeLog-2.5.35-lsm1
The LSM 2.5 BK tree can be pulled from:
bk://lsm.bkbits.net/lsm-2.5
2.5.35-lsm1
- merge with 2.5.31-35 (me)
- fix dnotify_struct leak (John Levon)
- added hooks for labelling during TCP passive open (Wayne Salamon)
- LIDS: update file open permission; compile fixes. (Huagang Xie)
- SELinux: ipc_permission fix (Stephen Smalley)
- SELinux: selopt fixes (Wayne Salamon)
- SELinux: sysctl updates (Stephen Smalley)
- update TCP passive open hook (Wayne Salamon)
- SELinux: rework sock security field usage (Wayne Salamon)
- SELinux: __FUNCTION__ fixes (Stephen Smalley)
- SELinux: bug fixes (audit and constaint evaluation) (Stephen Smalley)
- LIDS: __FUNCTION__ fixes (me)
- DTE: update to proper tasklist locking and iterators (me)
- LIDS: use new tasklist iterators (me)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
reply other threads:[~2002-09-17 19:58 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=20020917125720.K1972@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
/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®