From: Chris Wright <chris@wirex.com>
To: linux-security-module@wirex.com
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] 2.5.66-lsm1
Date: Mon, 31 Mar 2003 23:35:48 -0800 [thread overview]
Message-ID: <20030331233548.A7582@figure1.int.wirex.com> (raw)
The Linux Security Modules project provides a lightweight, general purpose
framework for access control. The LSM interface enables developing
security policies as loadable kernel modules. See http://lsm.immunix.org
for more information.
2.5.66-lsm1 patch released. This is a rebase up to 2.5.66 as well as
some interface and module updates. Out of tree projects will want to
resync with interface changes.
Full lsm-2.5 patch (LSM + all modules) is available at:
http://lsm.immunix.org/patches/2.5/2.5.66/patch-2.5.66-lsm1.gz
The whole ChangeLog for this release is at:
http://lsm.immunix.org/patches/2.5/2.5.66/ChangeLog-2.5.66-lsm1
The LSM 2.5 BK tree can be pulled from:
bk://lsm.bkbits.net/lsm-2.5
2.5.66-lsm1
- merge with 2.5.59-66 (me)
- restore file permission hooks to sendfile (Stephen Smalley)
- security.h inclusion in network files (Stephen Smalley)
- cleanup init[open]_private_file (Stephen Smalley)
- syslog, sysctl cleanups (Stephen Smalley)
- add CONFIG_SECURITY_NETWORK (Stephen Smalley)
- cleanup for newer skb allocation (me)
- SELinux: (Stephen Smalley)
- labelled network fixes
- ptrace fixes, drop support for exec_permission_lite
- minor fixes
- use kernel SID in reparent_to_init
- drop task_kmod_set_label hook (me)
- drop explicit exec_permission_lite hook (me)
- drop exta call to security_sock_rcv_skb hook (me)
- fix setfs[ug]id return values (Jakub Jelinek)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
reply other threads:[~2003-04-01 7:26 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=20030331233548.A7582@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®