[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <40B69F40.459.246EF0EB@localhost>
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: New security ezine released
Christian Ney <chris@...thell.org> wrote:
> There's only one way to find out: compile this stuff and use "strings
> BINARY|tail -2" on the binary, then your question should be answered
> completely, even without having to try it out (which I wouldn't advise you
> to do). ;)
There are easier/quicker ways than that...
If what you propose will be useful (which it will _IN THIS CASE_) then
simply "hex to binary" decoding the hex-ified overflow data blocks will
(normally) also work, as it did here and requires a much lighter
toolset than a full-blown build environment.
Regards,
Nick FitzGerald
Powered by blists - more mailing lists