pr0t0type said:

"I think it's dissapointing when an autohacker thread can reach 10+ pages while a buffer overflow tutorial thread struggled to hit 3 pages... "


I started this tutorial thread and it was very disappointing that no one had the skills on Windows, or did not want to participate. I have since completed it with screenshots and a C client, in addition to the perl script..

I also finished another on the wizip vuln that allows execution on double click. The POC that was released required you to open the archive first. Not so any more.

Does this mean I should not post it because the SKids will get it?

The winzip vuln could easily pose problems for worms and the like since hardly anyone is screening .uue files. You get a double dose of badness since it can execute on double click or any of the drag and unzips. You can't peek to see what's in it, and even if you could, you'd see nothing.

Where do we draw the line on restricting access to what is created or posted regardless of how moronic some of the batch files are.

There is good information released on this forum, why start being big brother and maybe miss out when a skiddy graduates and works something interesting out.

I'll be quiet now.

I also can just agree with this. Autohaxx0rs destroy everything, so it should be forbidden to make them public...

Ok FFS please stop brinign this up to the top again and again, short of that can an admin lock this thread please.

well first I think we should still compile exploits.
and second even I am one who made a bunch of autohaxers I am agree with the fact that auto haxer destroy the xploits.. those who can code them fine do it but do not publish it ...

goo dpoint mephisto