Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Ncat Users' Guide RFC
From: David Fifield <david () bamsoftware com>
Date: Mon, 16 Feb 2009 13:08:05 -0700

On Fri, Feb 13, 2009 at 05:09:31AM +0500, M. Shuaib Khan wrote:
You might want to elaborate the following paragraph in the "Command
execution" section a bit more. It isn't easily comprehended on the first
read. May be statement reordering is needed(?).

The --exec option (alias -e) takes as an argument the full pathname of the
command to be executed, along with any arguments. Apart from argument
splitting, the command is not interpreted, only executed with exec.
--sh-exec (-c) is the same, except that it executes the command by passing
it to */bin/sh -c*. That means that it's not necessary to use the full
pathname of the command if it lies in the PATH, environment variable
references are expanded, and any other shell interpretation is done.

Thanks for your suggestion. I reread the section and I agree that it was
not clear. I rewrote it with examples for both --exec and --sh-exec.

http://nmap.org/ncat/guide/ncat-advanced.html#ncat-command-exec

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault