>> There is a CAVEAT section in the man page that should also be
>> amended, I suspect.
>
>Heh, whoops. :)
There is more code that could be removed from main()
>From what I can tell, no traffic is actually generated on the initaiting
>machine.. nothing in tcpdump anyway.
>
Isn't that strange?
On Mon, Feb 06, 2012 at 04:47:45AM +, Mark Lumsden wrote:
> There is a CAVEAT section in the man page that should also be
> amended, I suspect.
Heh, whoops. :)
> Although useless on the initaiting machine, is it of any use to
> be able to scan a range of UDP ports, for diagnotic reasons, and
There is a CAVEAT section in the man page that should also be
amended, I suspect.
Although useless on the initaiting machine, is it of any use to
be able to scan a range of UDP ports, for diagnotic reasons, and
to see what is received (or not) on the receiving machine? As in,
can anything be infer
On Fri, Sep 09, 2011 at 03:04:19AM -0400, Brynet wrote:
> I think this was a feature, right? :-)
Here it is again, this time with the man page bits.
UDP port scanning doesn't make much sense, so prevent -u and -z from
being used at the same time.
ok?
-Bryan.
Index: nc.1
===
Hi Tobias,
Tobias Ulmer wrote on Tue, Jan 31, 2012 at 04:37:23AM +0100:
> - Remove confusing unused len fields from TAG and ENTRY
> - Remove a couple of internal unused variables
> - Prevent parse_path() from inserting empty ENTRYs into the list,
> leading to a crash due to negative array acces
