From: Karim Yaghmour <karim@opersys.com>
To: Niels Provos <provos@citi.umich.edu>, LTT-Dev <ltt-dev@shafik.org>
Cc: linux-kernel@vger.kernel.org, marius@umich.edu
Subject: Re: systrace for linux
Date: Fri, 18 Oct 2002 15:49:00 -0400 [thread overview]
Message-ID: <3DB065AC.A18F1BD@opersys.com> (raw)
In-Reply-To: 20021018191057.GJ1704@citi.citi.umich.edu
Hello Niels,
This is the sort of facility which can easily go on top of the existing
LTT infrastructure (http://www.opersys.com/LTT) since most of the events
you need are already cleanly caught by LTT. If we'd reintegrate the
event callback mechanisms we removed on Ingo Molnar's request (albeit
exporting them as GPLonly this time), systrace would then be easily
maintained as a loadable kernel module. In addition, since LTT already
has appropriate hooks for 6 architectures, systrace would immediately
become available on those archs (i386, PPC, S/390, ARM, MIPS, SH).
Karim
Niels Provos wrote:
> Marius A. Eriksen just finished the Linux port of systrace. You can
> find the kernel patch at
>
> http://www.citi.umich.edu/u/provos/systrace/linux.html
>
> Systrace is a fine grained sandbox for applications and system services.
> It supports interactive policy generation, intrusion detection, policy
> enforcement, privilege elevation, etc. More information at
>
> http://www.citi.umich.edu/u/provos/systrace/
>
> Comments are appreciated.
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
prev parent reply other threads:[~2002-10-18 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:10 systrace for linux Niels Provos
2002-10-18 19:49 ` Karim Yaghmour [this message]
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=3DB065AC.A18F1BD@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=marius@umich.edu \
--cc=provos@citi.umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.