Creating a USB bootable distribution isn't anything new. I have 3 1Gb keys one with OpenBSD (http://www.azbsd.org/~marco/openbsd/flashkeyinstaller/) , one with Linux loaded with an assortment of tools similar to Backtrack but with different tools I found more useful then those on BT, e.g, W3AF, Webscarab, and a variety of self created VoIP testing tools.

I contemplated making a security bootable distro, but so many variations of "security" are involved. Since I work in the VoIP arena, most of the tools I would need wouldn't do much for the information security pentester. I believe throwing one too many tools leads to bloat as well.

What are your thoughts on a variety of BT like pentesting USB's... Do you perceive the need for one, say a WebApplication pentesting USB, VoIP security testing USB... I could try to throw something together, but again, industries differ, testing differs, my opinions of tools would vary from the norm....

Hey silxp,

First of all, it sounds like a great new thread.  

There is a great distro for web app, Samurai WTF. My opinion is that a VoIP distro might just be a cool tool that many would want to try. And I don't think anyone else has done a VoIP Distro (VD). You could even use this as a slogan:

Have you gotten VD?  

Don

I decided to make a build based of Linux Mint of which I will streamline. So far this is my line-up:

Asteroid (listed first cause I wrote it ) XTest - w/Sample PCAPS, SIPFun VoIP Hopper, SIP Flanker, SIP Viscious, sip-proxy-kill.pl, rtp-proxy.pl, sip-redirect.pl, sip-kill.pl, sip-scan.pl, SIPSAK, PCAPSIPDump, Ork Audio, Oreka, ARPWatch, RTP Insert Sound, RTP Mix Sound, SIP Rouge, Spitter, Authtool, Erase Registrations, Redirect Poison, SIP Teardown, UDP Flood, VLAN Ping, Add Registrations, Check Sync Reboot, IAX Flood, Invite Flood, Reg Hijacker, RTP Flood, Netdude, Scapy, IAX Brute, IAX Auth Jack, IAX Hangup, RTP Inject, SIP Tastic, VSAP, h225 RegReject, VNAK, Seagull, ILTY, SIPp, SIP Crack, SIP Bomber, Enum IAX, OhrWurm, Wist, IWAR, TFTP Bruteforce, Fragrouter

I need to sort out how to position tools, e.g. Pentesting, DoS, Hijacking, etc., VoIP pentesting is a little different from the typical Application level pentesting since there is a little more involvement in different protocols, e.g., SIP vs. IAX. So hopefully I can lay out a framework for this. e.g, IAX Testing, SIP testing, h323 testing or something.

My feelings are, some will definitely find some of the stuff I can throw together useful, but the last thing I need are dozens of emails a-la "how can I hax0rfy my girlfriend's Vonage account". Anyhow, I will try to mimic (to a degree) what Backtrack has done without anyone claiming "clone". I'd like to keep things specific to VoIP, but the fact is, I will have to add a variety of scanners and other non VoIP specific tools (e.g. Scapy for packet injection, fragrouter).

I will also attempt to email the authors of tools I select to make sure they're fine with the use of their tools. Outside of the whole spectrum of open source licenses, I think back to the days of asking for permission to mirror/use someone elses work....

Any thoughts on names? VD sounds catchy But... If it were to evolve into something people on the corporate level would want, I know I would have a difficult time keeping a straight face while explaining to management why I have a "VD server"