Date: Fri, 22 Dec 2000 02:10:03 -0800 (PST) From: Peter Pentchev <roam@orbitel.bg> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/23740: kernel DoS tha could be executed by any user Message-ID: <200012221010.eBMAA3v42846@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/23740; it has been noted by GNATS. From: Peter Pentchev <roam@orbitel.bg> To: Charlie Root <iasenkk@hotmail.com> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/23740: kernel DoS tha could be executed by any user Date: Fri, 22 Dec 2000 12:08:46 +0200 On Fri, Dec 22, 2000 at 02:00:01AM -0800, Charlie Root wrote: > The following reply was made to PR kern/23740; it has been noted by GNATS. > > From: Charlie Root <iasenkk@hotmail.com> > To: freebsd-gnats-submit@FreeBSD.org, iasenkk@hotmail.com > Cc: > Subject: Re: kern/23740: kernel DoS tha could be executed by any user > Date: Fri, 22 Dec 2000 11:59:35 +0200 > > Addon :) > > I think that the kernel should not execute "panic" but to manage some > how with the problem. > And also I think it's not just fork problem , but "memory allocation" or > "user limits check" problem. Uhm - "user limits check" problem? Right on! So you think the kernel should enforce some kind of limits - you're exactly right. There should be a way to tell it what to do, what limits to impose on what users, now wouldn't that be a nice idea! Uh.. wait.. it already does that.. man 5 login.conf :) How exactly do you expect the kernel to know which limits to impose on what users 'by itself'? login.conf *is* the way to tell it. G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012221010.eBMAA3v42846>