From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: bohdan@kivc.vstu.vinnica.ua,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: isolating process..
Date: Thu, 7 Jun 2001 08:40:06 -0500 (CDT) [thread overview]
Message-ID: <200106071340.IAA59373@tomcat.admin.navo.hpc.mil> (raw)
--------- Received message begins Here ---------
>
> On Wed, Jun 06, 2001 at 09:57:25PM +0200, Erik Mouw wrote:
>
> >> Is it possible by any means to isolate any given process, so that
> >> it'll be unable to crash system.
> > You just gave a nice description what an OS kernel should do :)
> * Sigh * :-)
>
> > > Please, supply ANY suggestions.
> > >
> > > My ideas:
> > >
> > > create some user, and decrease his ulimits up to miminum of 1 process,
> > > 0 core size, appropriate memory/ etc.
> > That's indeed the way to do it.
> Byt how should I restrict him open socket and send some data (my IP,
> for example) somewhere ??
>
> I thinks I'll end up writing kernel module which will restrict all
> ioctls but few {mmap, brk, geteuid, geuid, etc..} for given UID.
You might look into the Linux Security Module project. It's not finished
but the hooks may give you what you need to start. See
http://mail.wirex.com/mailman/listinfo/linux-security-module
BTW, it is not possible to gurantee the process can't crash the system
unless there are no other processes...
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-06-07 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 13:40 Jesse Pollard [this message]
2001-06-07 14:28 ` Russell King
2001-06-07 14:27 ` Bohdan Vlasyuk
-- strict thread matches above, loose matches on Subject: below --
2001-06-05 9:37 Bohdan Vlasyuk
2001-06-06 19:57 ` Erik Mouw
2001-06-07 6:57 ` Bohdan Vlasyuk
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=200106071340.IAA59373@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=bohdan@kivc.vstu.vinnica.ua \
--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®