Re: Nsock new engines

[Henri Doreau <henri.doreau () gmail com>]

2012/10/25 Rob Nicholls <robert () robnicholls co uk>:
> > I've added a couple ifdef WIN32 that seem to do the job.
> >
> > Does r30107 work for you?
>
> I just tried out Ncat (r30112) and it doesn't appear to work on Windows (it
> connects with a SYN, SYN-ACK, ACK sequence, but then Ncat doesn't show or
> send anything I type, and when I kill Ncat it sends a RST). I quickly tested
> the latest revision on Linux and it seems fine there. A slightly earlier
> build (r30065) of Ncat work fine on Windows. Is it the new nsock engine at
> fault, as almost all of the commits between the builds appear to be nsock
> engine related? I can't see a way to force the nsock engine for Ncat as a
> workaround.
>
> Rob
Hi,

thanks for the feedback. I'll try to troubleshoot that. Which command
are you using? You should be able to force the use of a given engine
using the "--nsock-engine=select" parameter. Could you test it (server
and client side)?

Regards

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