Hi,No, you didn't.
Maybe I missed something here...
You're never going to find that out, Gregory, because mitch, our l33t code monkey, is keeping the code to himself. Now mind you, he *assures* us that it's easy to 'sploit, so we're just gonna have to take his word for it.I'm an assembler jockey from BITD and I know a few things about alloc/ calloc/malloc and heaps and stacks etc. So what's the key, may I ask, to this heap exploit that was the origin of this thread?
Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html