From: Jes Sorensen <jes@wildopensource.com>
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: 04 Mar 2004 04:40:26 -0500 [thread overview]
Message-ID: <yq0d67tt0fp.fsf@wildopensource.com> (raw)
In-Reply-To: <opr4bsvwbj4evsfm@smtp.pacific.net.th>
>>>>> "Michael" == Michael Frank <mhf@linuxmail.org> writes:
Michael> Just wondering on how to build a kernel-level facility which
Michael> would require shared libraries and executables to be "keyed"
Michael> or even "signed" to run on linux.
Michael> This is to prevent execution of software not specifically
Michael> authorized.
The shared libraries are going to cause you 'issues' since these are
all loaded by dynamic linker. All the kernel loads is ld.so, the
rest of them are mmap'ed from userland.
So if you want to take this approach, you would have to hack a special
ld.so that only allows your authorized libraries and only authorize
the kernel to load that dynamic linker. Otherwise you have to do
content validation for all mmap operations.
Jes
prev parent reply other threads:[~2004-03-04 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:10 How to black list shared libraries and executable Michael Frank
2004-03-04 8:35 ` Chris Wright
2004-03-04 9:40 ` Jes Sorensen [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=yq0d67tt0fp.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--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