From: Chris Wright <chrisw@osdl.org>
To: Michael Frank <mhf@linuxmail.org>
Cc: kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: How to black list shared libraries and executable
Date: Thu, 4 Mar 2004 00:35:46 -0800 [thread overview]
Message-ID: <20040304003546.U22989@build.pdx.osdl.net> (raw)
In-Reply-To: <opr4bsvwbj4evsfm@smtp.pacific.net.th>; from mhf@linuxmail.org on Thu, Mar 04, 2004 at 03:10:34PM +0800
* Michael Frank (mhf@linuxmail.org) wrote:
> Just wondering on how to build a kernel-level facility which would
> require shared libraries and executables to be "keyed" or even
> "signed" to run on linux.
Take a look at Cryptomark or DigSig. They at least cover the
executables bit.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-03-04 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:10 Michael Frank
2004-03-04 8:35 ` Chris Wright [this message]
2004-03-04 9:40 ` Jes Sorensen
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=20040304003546.U22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
/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®