From: richard offer <offer@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Red Phoenix <redph0enix@hotmail.com>
Subject: Re: Linux C2-Style Audit Capability
Date: Mon, 06 Aug 2001 15:07:59 -0700 [thread overview]
Message-ID: <1634130000.997135679@changeling.engr.sgi.com> (raw)
In-Reply-To: <fa.hg36o7v.1076epo@ifi.uio.no>
In-Reply-To: <fa.i3h9gdv.45k3go@ifi.uio.no> <fa.hg36o7v.1076epo@ifi.uio.no>
* frm alan@lxorguk.ukuu.org.uk "08/04/01 09:24:11 +0000" | sed '1,$s/^/* /'
*
*> System calls are overridden by pointing sys_call_table[system call] to a
*> replacement function which saves off the data for auditing purposes,
*> then calls the original system call.
*
* Ugly but that bit probably ties in with all the other folks trying to put
* together a unified security hook set for 2.5
Simply wrapping the system calls isn't going to get a CAPP (or C2)
compliant audit implementation. It also isn't how the "unified security
hooks" (aka LSM, Linux Security Modules) are working.
SGI is working towards a CAPP compliant audit implementation under the LSM
framework, I'd suggest that you head over to http://lsm.immunix.org/ for
more details on LSM.
richard.
-----------------------------------------------------------------------
Richard Offer Technical Lead, Trust Technology, SGI
"Specialization is for insects"
_______________________________________________________________________
next parent reply other threads:[~2001-08-06 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hg36o7v.1076epo@ifi.uio.no>
[not found] ` <fa.i3h9gdv.45k3go@ifi.uio.no>
2001-08-06 22:07 ` richard offer [this message]
2001-08-04 23:01 Hank Leininger
-- strict thread matches above, loose matches on Subject: below --
2001-08-04 20:48 Elladan
2001-08-04 7:03 Red Phoenix
2001-08-04 9:23 ` Alan Cox
2001-08-04 16:46 ` Ralf Baechle
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=1634130000.997135679@changeling.engr.sgi.com \
--to=offer@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=redph0enix@hotmail.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®