<br><br><div class="gmail_quote">On Fri, Oct 16, 2009 at 2:01 PM, Mathieu Bouchard <span dir="ltr"><<a href="mailto:matju@artengine.ca">matju@artengine.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 16 Oct 2009, Andrew Faraday wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
WHYYYYY????<br>
</blockquote>
<br>
Yeah, frankly, it's a lot easier to eat all RAM in other ways.<br>
<br>
#N canvas 0 0 450 300 10;<br>
#X obj 6 27 loadbang;<br>
#X obj 6 8 namecanvas z;<br>
#X obj 6 46 until;<br>
#X msg 6 65 \; z obj 0 0 table foo 1000;<br>
#X connect 0 0 2 0;<br>
#X connect 2 0 3 0;<br><font color="#888888">
</font> </blockquote><div><br>OK, you're all welcome to crash my pd but not to run hostile code on my machine. Now, we now that the code posted my Claude can eat up our RAM but can it write to an executable region or do other really nasty things?<br>
On the other hand - does a fresh copy of Vanilla or extended offer simple ways to run system commands? If yes, no odd stack overflow methods are needed to hack a system.<br></div></div><br>Andras<br>