From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: linux-kernel@vger.rutgers.edu
Subject: Re: Sealing the kernel
Date: Tue, 26 Oct 1999 14:28:46 -0500 (CDT) [thread overview]
Message-ID: <199910261928.OAA41544@tomcat.admin.navo.hpc.mil> (raw)
>From: Aaron Sethman <androsyn@atomic-city.dev.powerize.com>
>On Tue, 26 Oct 1999, Dimitris Margaritis wrote:
>> Yes, John forgot to mention that we're assuming boot from a read-only
>> media such as a write-protected floppy or CD-ROM. We also assume
>> that the rc scripts, kernel, and all modules to be loaded at boot
>> time (before of course the sealing module) also reside on that medium.
>>
>> About your last point, yes, root can do a lot of nasty things, but by
>> sealing the kernel at least they are constrained to what's available
>> through kernel services. That may help presumably by disabling a lot
>> of stuff in the running kernel.
>Or even a better idea, compile the kernel without module support all
>together. Just hope that you don't have any of those blasted Plug and
>Pray devices.
It would be better (in general) to remove root as a privileged user.
Try
http://www.rsbac.de/rsbac/
for a possible implementation.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~1999-10-26 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199910261928.OAA41544@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=linux-kernel@vger.rutgers.edu \
/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®