Nmap Development mailing list archives
Re: [NSE] qscan first read timeout value too short?
From: David Fifield <david () bamsoftware com>
Date: Wed, 25 Aug 2010 21:24:02 -0600
On Wed, Aug 25, 2010 at 09:02:29PM -0600, David Fifield wrote:
I think it also makes sense to move the unconditional read in l_ncap_pcap_register. I'll do that if it doesn't look like it will cause problems.
Looking at this more closely, it appears that the code is a little tricky, reading packets in advance and keeping them ready for when a user-requested read comes in. I'm not going to mess with it now. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [NSE] qscan first read timeout value too short? jah (Aug 06)
- Re: [NSE] qscan first read timeout value too short? David Fifield (Aug 06)
- Re: [NSE] qscan first read timeout value too short? jah (Aug 06)
- Re: [NSE] pcap first read times out with sub second read timeouts jah (Aug 19)
- Re: [NSE] qscan first read timeout value too short? Luis MartinGarcia. (Aug 19)
- Re: [NSE] qscan first read timeout value too short? jah (Aug 20)
- Re: [NSE] qscan first read timeout value too short? David Fifield (Aug 23)
- Re: [NSE] qscan first read timeout value too short? jah (Aug 24)
- Re: [NSE] qscan first read timeout value too short? David Fifield (Aug 25)
- Re: [NSE] qscan first read timeout value too short? David Fifield (Aug 25)
- Re: [NSE] qscan first read timeout value too short? David Fifield (Aug 06)
