Re: Ncrack on exotic Windows-land

[ithilgore <ithilgore.ryu.l () gmail com>]

ithilgore wrote:

> Honestly, this is the first time I come across this bizarre behavior. I know of
> no other firewall which does anything similar. It goes against the RFC rules,
> against the rules of logic and potentially against the rules of the universe.
>
> Given that the windows firewall is, as you said, enabled by default and that
> ncrack is limited by the underlying network stack as it doesn't use raw sockets
> or other low-level stuff, I don't see any other solution at the moment, other
> than specifically instructing the users to disable the firewall for the time
> they are running ncrack (or else they will suffer a serious performance
> degradation). I really don't like this approach but anything else would require
> sending ha^H^H mails to Microsoft about changing the firewall's behaviour (and I
> have a feeling they might go unanswered).

<irony>
Great, it seems the guys over at Redmond "can't reproduce" the bug and thus the issue
is resolved: </irony>

https://connect.microsoft.com/WNDP/feedback/ViewFeedback.aspx?FeedbackID=470990

What can I say?

-- ithilgore


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