From: Martin Stricker <shugal@gmx.de>
To: selinux@tycho.nsa.gov
Subject: Re: seperate kernel modules
Date: Tue, 31 Jul 2001 00:28:44 +0200 [thread overview]
Message-ID: <3B65DF9B.922246F3@gmx.de> (raw)
In-Reply-To: 200107301242.f6UCgs620116@mailgate3.cinetic.de
king killer wrote:
> 1 (or 2 days ago) i read a text how to infiltrate a linux system thru
> modules and here comes my idea.
> the kernel modules themselves shall be separated.
> for example a sound driver does not need to be able to access any
> other io-ports then the ones needed to use sound.
You might want to take a look at HURD, a new micro-kernel based unix
kernel from the GNU project. Here only the most basic functions remain
in the kernel, everything else, i. e. file systems or peripheral
hardware, is handled by so-called servers which run in user space, not
in kernel space. A very interesting approach. For a ready-to-install
distribution see http://www.debian.org/hurd/ .
Best regards,
Martin Stricker
--
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2001-07-30 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 12:42 seperate kernel modules king killer
2001-07-30 22:28 ` Martin Stricker [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-31 3:18 Jonathan Day
2001-07-31 8:59 king killer
2001-07-31 10:47 ` Dale Amon
2001-07-31 12:46 ` Dale Amon
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=3B65DF9B.922246F3@gmx.de \
--to=shugal@gmx.de \
--cc=selinux@tycho.nsa.gov \
/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.