Developing and Sharing Tools for Professional Hackers<p><strong>By Joe Basirico</strong></p><p><a><img src="https://threatpost.com/sites/default/files/joe_basirico_2_1.jpg" alt="Joe Basirico" title="Joe Basirico" style="float: left;" border="0" height="100" width="100" /></a>Professional hackers or security testers tend to write a lot of code. We write exploit code, fuzzers, code to handle esoteric protocols and data structures, unpackers, disassemblers, reversers, parsers, and so much more. We write this code because often what we're doing is so specific that is requires one off tools. Over time we develop an enormous arsenal of our own tools, scripts, functions and code snippets that make us significantly more efficient, but are hacks that are only beneficial to us.</p><p>We then turn around and present them at conferences, we show off their magic in the hands of the original developer and the crowd goes wild and the ecosystem stops there, because they are unsupported, undocumented and nearly unreadable by anybody but the original author. I'd like to fix that.</p><p><a href="http://threatpost.com/en_us/blogs/developing-and-sharing-tools-professional-hackers-043012" target="_blank">read more</a></p>
Source:
Developing and Sharing Tools for Professional Hackers
