From: Chris Wright <chris@wirex.com>
To: linux-security-module@wirex.com
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] 2.5.30-lsm1
Date: Tue, 6 Aug 2002 15:21:53 -0700 [thread overview]
Message-ID: <20020806152153.A29152@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.30-lsm1 patch released. This is a rebase to 2.5.30 as well as the
continuation of merging LSM with mainline.
Full lsm-2.5 patch (LSM + all modules) is available at:
http://lsm.immunix.org/patches/2.5/2.5.30/patch-2.5.30-lsm1.gz
The whole ChangeLog for this release is at:
http://lsm.immunix.org/patches/2.5/2.5.30/ChangeLog-2.5.30-lsm1
The LSM 2.5 BK tree can be pulled from:
bk://lsm.bkbits.net/lsm-2.5
2.5.30-lsm1
- merge with 2.5.27 (Greg KH)
- merge with 2.5.28-30 (me)
- bk file merging to handle changes from mainline (Greg KH)
- removed BUS_ISA declaration (Greg KH)
- add settime hook (Robb Romans)
- SELinux: Bug fixes for the PSID mapping code. (Stephen Smalley)
- update initlialized to C99 sytle for cap and dummy (Adam)
modules.
- Fix memory leaks in IPC LSM hooking. (Stephen Smalley)
- Fix file_lock hooks. (Matthew Wilcox)
- update modules according to file_lock hook change (me)
- DTE: logic cleanups (Serge Hallyn)
- SELinux: cleanup sysctl table (Chris Vance)
- __FUNCTION__ cleanup (Anton Blanchard)
- remove __exit attribute from selinux_nf_ip_exit (me)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
reply other threads:[~2002-08-06 22:20 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=20020806152153.A29152@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®