7 Commits

Author	SHA1	Message	Date
sean	17f7791c02	General File cleanup. Added closing paren for the port error message	2012-08-04 01:18:40 +00:00
sean	ce2f251cd5	Added a function to check if port specification will do anything. Changed over my logic to use this new functioni. (scan_mode_uses_target_ports)	2012-08-04 01:08:31 +00:00
sean	256bffba9c	Removed the requirement from is root in the error message about having a useless -p option	2012-08-04 00:52:36 +00:00
sean	a9a6c431cd	Added an error message when the user runs nping in a priviliged mode and specifies a port. I choose to add an error message to keep nping's behavior inline withnmaps.	2012-08-04 00:41:02 +00:00
fyodor	684f42c4ad	One more adjustment to the license text. Notes that Zenmap, Ncat, and Nping use this license. Note that contributions made directly in the src repository are treated the same as those in the mailing list.	2012-03-01 06:53:35 +00:00
fyodor	e96a7b7b24	Update the headers for each code file. This updates code copyright dates to 2012, notes the awesome NSE in the list of technology, and slightly rewords the derivative works clarification	2012-03-01 06:32:23 +00:00
david	ed2ba4e168	Copy nping, nsock, nbase, zenmap, ncat from their homes in /. ... If you have trouble updating after this revision you need to follow these instructions. You have probably just seen an error like this: svn: URL 'svn://svn.insecure.org/nping' of existing directory 'nping' does not match expected URL 'svn://svn.insecure.org/nmap/nping' This is caused by the replacement of SVN externals. Here's what you need to do. First, save any local changes you might have in the nping, nsock, nbase, ncat, and zenmap directories. (For example by running "cd nping; svn diff > ../nping.diff".) If you don't have any local changes you can skip this step. Then run these commands: rm -rf nping/ nsock/ nbase/ ncat/ zenmap/ svn update svn cleanup If all else fails, you can just delete your whole working directory and check out anew: svn co --username guest --password "" svn://svn.insecure.org/nmap There may be further discussion in the mailing list thread at http://seclists.org/nmap-dev/2011/q4/303.	2011-11-16 21:49:44 +00:00