Skip to contentSkip to conversation

seperate kernel modules

DISCUSSION king killer 2 participants 2 messages Jul 30, 2001 SELinux security module

lore
Share & tools
lore
#0 lore raw

hello
im new here so im sorry if i say something someone else has already proposed
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.
______________________________________________________________________________
Flug.de | Wer oft unterwegs ist, kann keine Zeit verschwenden
http://flug.de/sb/?PP=0-5-100-105-11

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 5 lines · king killer

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

Signature · 7 lines
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 [email protected] with
the words "unsubscribe selinux" without quotes as the message.