Nmap Development mailing list archives

Re: Reg: Clarification of my question


From: Dario Ciccarone <dciccaro () cisco com>
Date: Wed, 11 Jan 2017 11:09:22 -0500

I gave a networking primer - I didn't focus on IPv4 vs IPv6.

So you would have a new option - "nmap -sM", for "ML scan". Which would
then proceed to invoke magic(), and based on what magic() returns, it
would choose UDP or TCP (wondering why limiting to those two protocols)
as L4, and I also assume will choose the ports.

Can you pseudocode magic() for us ? What would be the inputs into it?
The outputs, we kind of figure out. How would it build a decision tree
to decide what the output should be ?


On 1/11/17 11:04 AM, Akash Das wrote:
Dear dario,

I think you got the question wrong. I just wanted to ask that a new
feature can also be added which will choose which connection to use
TCP or UDP . I am not at all talking about IPv4 and IPv6 here. 
I was just suggesting that instead of specifying everytime which type
of connection to use I just wanted to say on the basis of the network
architecture can there be an option which chooses the best type of
connection either UDP or TCP.
We can introduce ML into this concept also. 
I think you got my question wrong.

Thanks for replying,

With Regards,
-- 
/*Akash Das
*/
/*Student Systems admin
*/
/*Indian Institute Of Information Technology
*/
/*Sricity*/


_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: