Would raising the number of NMBCLUSTERS help? Or would it just postpone
the problem? Solaris/x86 also does not have any problems with the code.
-Kip
On Mon, 9 Aug 1999, Marc Olzheim wrote:
> > Isn't this a huge problem for ordinary users on a system?? I mean
> >
> Isn't this a huge problem for ordinary users on a system?? I mean
> there aren't any user restrictions on sockets right? I imagine
> there will be some sort of follow up on this exploit?
Well, there is a 256k limit per socket of the buffer (I & O), try
sysctl kern.maxsockbuf and you can limit
On Mon, 9 Aug 1999, Marc Olzheim wrote:
> >
> > I'm running 2.2.6 and this program WREAKED havoc on it :)
>
> It seems to work on NetBSD 1.3.2 too
> Perhaps a BSD-ism ?
>
> Marc
>
Isn't this a huge problem for ordinary users on a system?? I mean
there aren't any user restrictions on soc
>
> I'm running 2.2.6 and this program WREAKED havoc on it :)
It seems to work on NetBSD 1.3.2 too
Perhaps a BSD-ism ?
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
I'm running 2.2.6 and this program WREAKED havoc on it :)
Rebooted and then when I tried delete the a.out I got
a page fault. I wasn't able to read it though because the
machine again rebooted :( Scary... I also got strange socket
errors after the machine was rebooted those two times...
-Greg
