Re: Shows when no limits are set or restricted shell or bat access

[KF_lists <kf_lists () secnetops com>]

I do not believe the point was to show that you can chew up system 
resources... although that IS a side effect. That was not the point.

Add a sleep statement in there if it makes you feel better.
-KF


Clairmont, Jan M wrote:
> ;;for %i in (*.exe) do start %i %n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n
> ;;for %i in (*.exe) do start %i AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.... (type as ;;much "A"-s as cmd.exe allows 
> on one line.)
>
>
> Any system UNIX at least use to churn and eat system resources with a spawned
> shell, this is not new on any system.    With unlimited program execution  you can
> lock almost any system with a repeating shell program, but cute anyway.8->
>
>
> Jan Clairmont
> Unix Security Support/Consultant
>  
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html