From: "Michael Frank" <mhf@linuxmail.org>
To: "kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: How to black list shared libraries and executable
Date: Thu, 04 Mar 2004 15:10:34 +0800 [thread overview]
Message-ID: <opr4bsvwbj4evsfm@smtp.pacific.net.th> (raw)
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.
This is to prevent execution of software not specifically authorized.
Applications:
- Improve security
- License management
- Prevent unauthorized software installation
- Black-listing e.g. SCO libraries and executables
Regards
Michael
next reply other threads:[~2004-03-04 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:10 Michael Frank [this message]
2004-03-04 8:35 ` Chris Wright
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=opr4bsvwbj4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.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®