On Tuesday 27 October 2009 16:36:07 David Cottrill NCH Software wrote:
> To kill off a computer quickly:
> step one: ":(){ :|:& };:"
> step two: reboot because your machine has stopped responding
Actually, I ran that intentionally, as root, on my new 2x dual-core system
that I built in 2005. It
In <4ae7d2a7.9040...@hardwarefreak.com>, Stan Hoeppner wrote:
>Will Murnane put forth on 10/27/2009 5:23 PM:
>> This is also the wrong list; it's for users and developers of the
>> Debian Live scripts. Please re-post on the proper list.
>>
>> Will
>
>It may not be the most appropriate list for his
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 27, 2009 at 05:27:58PM +0500, surreal wrote:
> I just caught hold of a C source code from 2005. This code is a local DoS
> which fills up the entire memory on Linux 2.6.N kernels.
I guess you are talking about CVE-2008-5300 [1]. What happe
On Tue, Oct 27, 2009 at 08:27, surreal wrote:
> I just caught hold of a C source code from 2005. This code is a local DoS
> which fills up the entire memory on Linux 2.6.N kernels.
After about 15 minutes:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
16799 will 20 0
It may chew up an old computer but a new one won't really do more than
sniffle.
It goes on an endless loop sending short messages to itself which aren't
very long. If you wanted to kill a modern computer with that script
you'd have to set ma=some large number.
It can't kill off a modern mult
On Tue, 27 Oct 2009 09:33:15 -0500
"Boyd Stephen Smith Jr." wrote:
...
> (:(){:&:;};:) at a shell prompt should peg all your CPUs and run you
> out of process ids.
For more information on fork bombs, including an annotated one closely
resembling Boyd's, see:
http://en.wikipedia.org/wiki/Fork_b
In <8857b3150910270527p4d18d958mc2034eed29dc3...@mail.gmail.com>, surreal
wrote:
>I saw that RAM wasent running out, but the CPU usage was 100%. I didnt wait
>for computer to hang, but I think this code is dangerous and can be used for
>malicious intentions.
If that's the only thing that happens,
surreal wrote:
I just caught hold of a C source code from 2005. This code is a local
DoS which fills up the entire memory on Linux 2.6.N kernels.
At that time, I used Fedora Core 4 and a pentium 4 machine with 512 MB
ram. After compiling and running this program on the old machine, it
used to
> I am sending the code so that we can prevent bad use of it. It still has
> potential of a local DoS. I hope kernel hackers might get interested in
> this.
Shouldn't it be sent to a kernel mailling-list then?
--
() ascii-rubanda kampajno - kontraŭ html-a retpoŝto
/\ ascii ribbon campaign - ag
9 matches
Mail list logo
