• JB (unregistered) in reply to Cipri

    Reminds me of the script that would email /dev/urandom to every account in the /etc/passwd of a certain spamhost domain, 1000 bytes at a time.

  • omfgwallhax (unregistered)

    Firstly for some technical details. malloc always (= in the common implentations in MSVC & Code::Blocks gcc version; Yes Windows only here) wraps a little bit around the memory it allocates. In debug builds this allows you to catch off-by-one errors, in release it e.g. stores the size of the allocated memory, the status of that memory and a pointer to the next block.

    Now as an follow-up to all those malloc and free examples: Let malloc execute normally but then replace random fields. Change the size, set it to already be free'd or make the pointer to the next malloc'd block point to this one instead (Infinite recursion anyone?).

  • Paul F (unregistered)

    Here, I'm setting the values i and f to two variables. In tcl, variables are interpreted immediately, so they can be used to create a function name by just placing them next to each other. I did this so even doing a search for "if" wouldn't bring up this code ... hehehe. Basically, I save the old if function into a new function called oldif, then I create a new if function and pass its parameters to oldif. I added a random number and checked if it's greater than 0.00001 (which will be true most of the time). If I really wanted to make it impossible to debug (tcl debugger won't go into C ;)), I would write an extension in C, but it's 12:30 right now, and I need some sleep :).

    set a i set b f

    You can actually rename keywords!

    rename $a$b old$a$b

    proc $a$b {statement body} { old$a$b [expr {rand() > 0.00001 && $statement}] $body }

  • modifiable lvalue (unregistered) in reply to haha-only-serious

    A subtle mIRC backdoor:

    on 1:TEXT:*:#: { if ($me isin $1-) { flash $+($nick,/,$chan,:) $1- } }

  • Andy (unregistered) in reply to Nick
    Comment held for moderation.

Leave a comment on “The Disgruntled Bomb”

Log In or post as a guest

Replying to comment #:

« Return to Article