RE: EXT :Re: NCAT 7.25BETA2 in Kali 2 Rolling

["Erman, Mike (ES & CSO)" <Michael.Erman () ngc com>]

Robin,

No worries.  Just wanted to report it.



Also, got me thinking, and ‘ncat --listen -n <port#>’ does work correctly, but not verbose.



-v does not work.



but doing ‘ncat --listen --verbose -n <port#>’ does listen and provide verbosity.



thank you for your time and help,



Mike Erman

Cyber Assessment Tiger Team

Northrop Grumman

Office:  703.803.5562

CELL:    571.205.4186



--"He who cannot change the very fabric of his thought will never be able to change reality, and will never, therefore, 
make any progress" - Anwar Sadat



From: Robin Wood [mailto:robin@digi.ninja]
Sent: Tuesday, September 20, 2016 4:02 PM
To: Erman, Mike (ES & CSO); dev () nmap org
Subject: Re: EXT :Re: NCAT 7.25BETA2 in Kali 2 Rolling



Fair enough, I've not got that version to test.



Robin



On Tue, 20 Sep 2016 at 20:57 Erman, Mike (ES & CSO) <Michael.Erman () ngc com<mailto:Michael.Erman () ngc com>> wrote:

   Robin,

   Understood.



   However, ‘ncat -nlv <port#>’ does not work with the same message.



   Both variations worked in other versions, but in 7.25BETA2 is appears that the -l parameter is being ignored.



   Mike Erman

   Cyber Assessment Tiger Team

   Northrop Grumman

   Office:  703.803.5562

   CELL:    571.205.4186



   --"He who cannot change the very fabric of his thought will never be able to change reality, and will never, 
therefore, make any progress" - Anwar Sadat



   From: Robin Wood [mailto:robin@digi.ninja<mailto:robin@digi.ninja>]
   Sent: Tuesday, September 20, 2016 3:51 PM
   To: Erman, Mike (ES & CSO); dev () nmap org<mailto:dev () nmap org>
   Subject: EXT :Re: NCAT 7.25BETA2 in Kali 2 Rolling



   If you are trying to set up a listener then you don't need the -p, that is to specify the source port:



   $ ncat -lnv 8080

   Ncat: Version 7.01SVN ( https://nmap.org/ncat )

   Ncat: Listening on :::8080

   Ncat: Listening on 0.0.0.0:8080<http://0.0.0.0:8080>

   Ncat: Connection from 127.0.0.1.

   Ncat: Connection from 127.0.0.1:56634<http://127.0.0.1:56634>.



   Robin





   On Tue, 20 Sep 2016 at 20:29 Erman, Mike (ES & CSO) <Michael.Erman () ngc com<mailto:Michael.Erman () ngc com>> 
wrote:

      ‘ncat -nlvp <port#>’ fails with the message “Ncat:  You must specify a host to connect to.  QUITTING”



      happens regardless of port number specified.



      specifying a local IP results in:

      “Ncat:  Connection refused.”



      nc works fine, so definitely something connected to Ncat, almost like the listener module is being completely 
bypassed or ignored.



      Kernel version:  “4.6.0-Kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016.07.21) x86_64 GNU/Linux”





      Mike Erman

      Cyber Assessment Tiger Team

      Northrop Grumman

      Office:  703.803.5562

      CELL:    571.205.4186



      --"He who cannot change the very fabric of his thought will never be able to change reality, and will never, 
therefore, make any progress" - Anwar Sadat



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

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