Requesting Suggestions for MyNmap Enhancements
I am brainstorming on where the project should go. There are a few bugs that need fixing, the most glaring of these is a race condition where a scan doesn’t complete and the file is perpetually trying to be parsed by the back end loader. I have been toying with the idea of rewriting the PERL code so that the application is entirely written in PHP, I just feel the whole architecture of mixing programming languages is a little ugly. The scheduling interface, while functional, is very clunky. And finally there have been a lot of improvements in Nmap that the tool doesn’t take advantage of, like LUA scripts.
I am open for suggestions and feature requests right now, please comment if you have an idea!
by tag
by anthony
The virtual machine is handy. I believe an ESX version would be very well received. (at least by me !)
by JD
Have a way to kill scans, that are stuck “in progress”. By the way, how do I kill a scan that is stuck “in progress” now? Very excellent tool. Cheers.
by Stefan
I’m also having troubles running the virtual machine under ESXi, so I think an ESX(i) Image could be really helpful. Especially as ESXi is now free and many people also use this platform.
by m0te
I absolutely love MyNmap so far, but agree with your ideas. I don’t particularly care about the “under-the-covers” stuff, just that it’s reliable and predictable. Taking advantage of LUA scripts is a must, IMO. I’d like to see a way to update Nmap independently of MyNmap. I cannot use MyNmap in a real network at the moment because of my unfamiliarity with OpenBSD. I’d love to see MyNmap released separately from the LAMP stack, so I could, for instance, install it on a Windows/AMP box. Maybe this all leads back to docs…
by chris
I would like to be able to “mark” a server that has been scanned as “approved”, meaning approved by security because it complies with the company policies. Then in future scans if the approved profile does not match what was approved it will notify via email or just flag the server in the webui.
To everyone that is asking for a ESX version of this virtual machine… it’s very easy to make yourself. Just my opinion, the author should only provide the VM as a Virtual Appliance, and it’s the users responsibility to convert it to ESX, Fusion, Hyper-V or whatever virtual platform you’re on.
So, here’s how you get it working on ESX. First, I think the OS was shutdown uncleanly. The VM is in a “dirty” state. Delete the .lck files and directory. These are lock files on the virtual machine. Then, boot the VM, log in as root and make a snapshot of the OS. Shut down cleanly (“halt”) and make sure you power it off in the VM console. The VM is now clean and ready to be converted to ESX’s virtual machine format.
Download Vmware Converter from http://www.vmware.com/products/converter (free), install and launch. Click on Convert. The “Source” is “other”. Browse to the VM. Set the destination as either your ESXi host or VIC server. That should do it! Good luck to all.
BTW I love this virtual machine. I would like to request the ability to kill a scan in progress. Thanks Todd for making such a kickass program.
The most important thing that I forgot to mention was a proper installer, something that makes the setup easy. Virtual machine images are nice, but it isn’t the most efficient way of running the application if you already have a server to use.