Nmap Development mailing list archives
Re: [RFC] Now Redoing Ncat's Output Options
From: Dirk Loss <lists () dirk-loss de>
Date: Sat, 11 Oct 2008 08:33:08 +0200
Kris Katterjohn wrote:
So anyway, Ncat has the following output options available: -o, --output (ASCII output) -x, --hex-dump (Hex output) I'm in favor of changing these to names resembling Nmap's output options. And not just because -x needs to be changed per the proxy discussion: I think that if there is going to exist more than one output option, they should be at least more similar in name.
Yes, lots of potential output formats could be thought of (useful or not): XML, ASCII with time-stamps or debugging information, output including just one side of the communication channel, non-ASCII characters replaced, maybe even syslog or PCAP...
My first thought is this: -oA (ASCII) -oH (Hex) Would this be confusing since Nmap has -oA for "all" log formats? What about using -oN instead? That may correspond better since ASCII is "normal."
I think -oA would be confusing for Nmap users. -oN seems more consistent too me. Especially because at the moment, the "ASCII ouput (-o)" can include binary data. I suggest calling it "normal output" (-oN) instead.
Regards Dirk _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- [RFC] Now Redoing Ncat's Output Options Kris Katterjohn (Oct 10)
- Re: [RFC] Now Redoing Ncat's Output Options Dirk Loss (Oct 10)
- Re: [RFC] Now Redoing Ncat's Output Options doug (Oct 10)
- Re: [RFC] Now Redoing Ncat's Output Options Dirk Loss (Oct 11)
- Re: [RFC] Now Redoing Ncat's Output Options Kris Katterjohn (Oct 11)
- Re: [RFC] Now Redoing Ncat's Output Options DePriest, Jason R. (Oct 11)
- Re: [RFC] Now Redoing Ncat's Output Options Kris Katterjohn (Oct 11)
- Re: [RFC] Now Redoing Ncat's Output Options Dirk Loss (Oct 11)