mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: linux-security-module@wirex.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.71-lsm1
Date: Mon, 16 Jun 2003 22:27:12 -0700	[thread overview]
Message-ID: <20030616222712.C15289@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.71-lsm1 patch released.  This is an update up to 2.5.71 as well as
some module updates, and various cleanups.  In line with other struct
sock changes in 2.5.71, the sock->security field is now called
sk_security.

Full lsm-2.5 patch (LSM + all modules) is available at:
	http://lsm.immunix.org/patches/2.5/2.5.71/patch-2.5.71-lsm1.gz

The whole ChangeLog for this release is at:
	http://lsm.immunix.org/patches/2.5/2.5.71/ChangeLog-2.5.71-lsm1

The LSM 2.5 BK tree can be pulled from:
        bk://lsm.bkbits.net/lsm-2.5

ChangeLog summary:

Chris Wright:
  o [SELINUX] update to new struct sock (struct members now prefixed with sk_)
    TAG: v2.5.71-lsm1
  o [LIDS] update to new struct sock (struct members now prefixed with sk_)
  o update to new struct sock (->security becomes ->sk_security)
  o trigger update.  Update to newer SendMail.pm, and set ReplyTo
  o merge with 2.5.71
  o [TPE] various cleanups
  o [LIDS] delete lids_check_scan.c, leftover from previous lids patch

Huagang Xie:
  o [LIDS] merge 2.0.3rc1 patch

Niki Rahimi:
  o [TPE] Update doc to reflect use of sysfs
  o [TPE] move to sysfs and fix bug in tpe_search
  o Updates to spin lock code
  o Added spin locks to tpe_acl

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

                 reply	other threads:[~2003-06-17  5:14 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=20030616222712.C15289@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®