* Re: isolating process..
@ 2001-06-07 13:40 Jesse Pollard
2001-06-07 14:28 ` Russell King
0 siblings, 1 reply; 6+ messages in thread
From: Jesse Pollard @ 2001-06-07 13:40 UTC (permalink / raw)
To: bohdan, Linux kernel mailing list
--------- 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.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: isolating process..
2001-06-07 13:40 isolating process Jesse Pollard
@ 2001-06-07 14:28 ` Russell King
2001-06-07 14:27 ` Bohdan Vlasyuk
0 siblings, 1 reply; 6+ messages in thread
From: Russell King @ 2001-06-07 14:28 UTC (permalink / raw)
To: Jesse Pollard; +Cc: bohdan, Linux kernel mailing list
On Thu, Jun 07, 2001 at 08:40:06AM -0500, Jesse Pollard wrote:
> --------- Received message begins Here ---------
> > Byt how should I restrict him open socket and send some data (my IP,
> > for example) somewhere ??
I believe that Netfilter will do this for you. Look at:
Owner match support (EXPERIMENTAL)
CONFIG_IP_NF_MATCH_OWNER
Packet owner matching allows you to match locally-generated packets
based on who created them: the user, group, process or session.
If you want to compile it as a module, say M here and read
Documentation/modules.txt. If unsure, say `N'.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* isolating process..
@ 2001-06-05 9:37 Bohdan Vlasyuk
2001-06-06 19:57 ` Erik Mouw
0 siblings, 1 reply; 6+ messages in thread
From: Bohdan Vlasyuk @ 2001-06-05 9:37 UTC (permalink / raw)
To: linux-kernel
Hi !
Is it possible by any means to isolate any given process, so that
it'll be unable to crash system. Suppose all the process needs is
stdin, stdout, and CPU time. Can Linux guarantee that given process
won't hurt system stability ? Let us soppose that we have ideal CPU
without mistakes. How can I limit CPU time/Mem Usage for given
process?
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.
Thanks!
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: isolating process..
2001-06-05 9:37 Bohdan Vlasyuk
@ 2001-06-06 19:57 ` Erik Mouw
2001-06-07 6:57 ` Bohdan Vlasyuk
0 siblings, 1 reply; 6+ messages in thread
From: Erik Mouw @ 2001-06-06 19:57 UTC (permalink / raw)
To: Bohdan Vlasyuk; +Cc: Linux kernel mailing list
On Tue, Jun 05, 2001 at 12:37:55PM +0300, Bohdan Vlasyuk wrote:
> Is it possible by any means to isolate any given process, so that
> it'll be unable to crash system. Suppose all the process needs is
> stdin, stdout, and CPU time. Can Linux guarantee that given process
> won't hurt system stability ? Let us soppose that we have ideal CPU
> without mistakes. How can I limit CPU time/Mem Usage for given
> process?
You just gave a nice description what an OS kernel should do :)
> 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.
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: isolating process..
2001-06-06 19:57 ` Erik Mouw
@ 2001-06-07 6:57 ` Bohdan Vlasyuk
0 siblings, 0 replies; 6+ messages in thread
From: Bohdan Vlasyuk @ 2001-06-07 6:57 UTC (permalink / raw)
To: Linux kernel mailing list
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.
thank, thought.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-06-07 14:33 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-06-07 13:40 isolating process Jesse Pollard
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
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®