Re: oops, previous message broken

2001-03-20 Thread Ɓukasz Grochal
Stefan Laudat <[EMAIL PROTECTED]> writes: > oops, fixed version attached... Nice try... now examine the loop in which fork() is called. the first instance calls 30 processes, which in turn call 29, 28... and so on children. In effect you generate a pretty nice DoS on both source and victim hosts

oops, previous message broken

2001-03-19 Thread Stefan Laudat
oops, fixed version attached... lost myself in details sorry. -- Stefan Laudat - Network & Security Engineer CCNA,CCAI RoEduNet - THE Romanian Education Network --- If you're not part of the solution then you're part of the problem. muci.pl