Re: [Nmap-scanner-general] encoding problem

[Max <nm...@we...>]

Hi Matthias,

I noticed a bug with 4.03 that is solved in 4.20 that happens if you
specify an nmap command-line with -sS and -sU and a port list with -P
N,N1, etc

the bug is that nmap outputs a warning message about 'UDP port scan
requested, but no UDP ports specified; skipping'

If you could, please upgrade to version 1.0 of Nmap-Scanner and re-run
your script, one of the fixes I did with 1.0 was to improve the
modules' error reporting .. .9 and earlier don't catch and report the
stderr from nmap properly, 1.0 does (from my testing).

Let me know what the results are after upgrading, and if the issue
persists please post code that you are using to the list so I can help
troubleshoot it / test it in my own environment to try to figure out
what is happening.

Thanks,
Max

On 10/31/06, Matthias Waehlisch <mw...@fh...> wrote:
> > $Nmap::Scanner::DEBUG = 1;
> >
>   Unfortunately it haven't any effect.
>
>   Yes, you are right ... I downgrad XML::SAX to version 0.12 and the empty
> <nmap-msg></nmap-msg> field was filled.
>
>   It says that file or directory name is wrong - I don't know why. I will
> try to look on it.
>
> > What happens when you run the command line below on your windows host?
> >  What output do you get?
> >
>   That's the strange point. If I exactly execute the cmdline everything
> works fine.