Nmap Developmentmailing list archives

By Date

By Thread

Re: Ncat proposal: new environment variables

I had a meeting with David this Tuesday and was assigned to implementthe proposal from my previous post, without ncatin/ncatout FD numbersyet (I will probably be adding them next week). So, here's a list ofenvironment variables that I introduced to the--exec/--sh-exec/--lua-exec child processes (along with a quote fromthe docs written by me): * NCAT_REMOTE_ADDR - the remote address - in connect mode, it's theone we're connecting to, in listen mode - it's the one that connectedto us, * NCAT_REMOTE_PORT - the remote port number, where "remote" means thesame as above, * NCAT_LOCAL_ADDR - our local address used forestablishing/receiving the connection, * NCAT_LOCAL_PORT - our local port number, * NCAT_PROTO - the protocol name - TCP, UDP or SCTP, * NCAT_SSL - set to "1" if we're using SSL. Not set otherwise.In addition to the code (which works under Windows as well) and itstests and documentation, I also added some examples. This includes ap0fme.py script, which tells the connecting user everything it couldgather on her, using TCP fingerprinting (requires an external tool -p0f, see:http://lcamtuf.coredump.cx/p0f3/ ). There's also a simpleshell script demonstrating logging and a Lua "whatismyip" script.Feel free to pull the nmap-exp/d33tah/ncat-env-conninfo branch, try itout and - if you have some time - read the diff (against r31368).Feedback is more than welcome! :)I'm also really interested about the Ncat tricks you invented thatmake use of these variables.--Jacek Wielemborek_______________________________________________Sent through the dev mailing listhttp://nmap.org/mailman/listinfo/devArchived athttp://seclists.org/nmap-dev/

By Date

By Thread

Current thread:

• Ncat proposal: new environment variablesJacek Wielemborek (Jul 10)
  • Re: Ncat proposal: new environment variablesJacek Wielemborek (Jul 19)
    • Re: Ncat proposal: new environment variablesDavid Fifield (Jul 23)