On Monday 10 November 2008 04:10:34 Ron wrote: > Hi everybody, > > Just subscribed to this list because I have a question that I figure you > guys have come across before. Hopefully you can save me some time (and a > lawsuit or two :) ). > > I'm currently adding vulnerability checks to Nmap using the scripting > engine. So far, I've been basing them on scripts that people put online > without licensing (I don't base them on the code, just on the network > traffic). > > I'd like to add support for other Windows vulnerabilities, though. For > example, having a check for ms06-040 would be really nice. However, I > can't find any free checkers (and even GPL, without special > accommodations, is incompatible with Nmap's license). Even with > ms08-067, I'm using a check that's used by Metasploit, but it crashes > over 50% of systems, which is definitely not good. Foundstone and Nessus > have better ones, but their licensing makes it prohibitive. > > Which leads me to my question -- I have no interest in looking at the > source for checks done by, say, Foundstone or Nessus. However, looking > at their network traffic and reproducing their checks can be extremely > helpful. But I don't know how licensing works, in this case -- does the > licensing on their code apply to network traffic with Windows, or does > the licensing end at the sourcecode level? > > I'd like to add the same checks as them at the traffic level, but I > don't want to violate licenses. > > Can somebody here tell me where the line between violations/fair use is > drawn in this case? With the nature of OpenVAS, you must have run across > this before.
The licensing will be in relation to the source code, OTOH you need to be in a position where you have a license on the source code that allows you to execute it for the purposes you have outlined. That means for example that if you're working on nmap scripts for $corp based on Nessus, that $corp has an appropriate license to allow generation of packets from Nessus. Note also that depending on your locality, various EULA could have further impact on how you are allowed to use the results (such as packet captures) from commercial tools. Just for kicks, my colleague is the one who wrote the original code (http://labs.portcullis.co.uk/application/ms08-067-check/) on which Metasploits check for MS08-067 is based so I could probably get it ported relatively easily. OTOH, the check we (OpenVAS) use is based on earlier packet analysis by one of the guys in India of traffic captured by myself using a port of the original POC to Samba's RPC client (http://www.nth-dimension.org.uk/blog.php?id=72). Traditional reverse engineering style really, one person examines the code, documents (in this case as .pcap's) what happens and then someone else goes off and writes the check. Essentially, the checks *I* write are either for things I have discovered, things where I can write a check based on an advisory, or things where I can reverse engineer what is going on from packet level dumps. For obvious reasons, I stay clear of looking at how Nessus 3.x does things. Cheers, Tim -- Tim Brown <mailto:[EMAIL PROTECTED]> <http://www.nth-dimension.org.uk/> _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
