Nmap Development mailing list archives

Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly

From: Tomas Hozza <thozza () redhat com>
Date: Fri, 8 Feb 2013 03:12:45 -0500 (EST)

----- Original Message -----

Looks good, thanks. Can you add a test along the lines of the one
added by Michal Hlavinka for a similar EOF issue?

http://seclists.org/nmap-dev/2012/q4/337
http://seclists.org/nmap-dev/2012/q4/att-337/ncat-shutdown2.patch

David Fifield


Thank you for your reply. I added a new test and also fixed Michal's
test to reflect new behaviour with and without --recv-only option.
Attaching proposed patch for Ncat's testsuite.

Regards,

Tomas Hozza

Attachment: 0001-Ncat-Test-for-server-client-EOF-issue.patch
Description:

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

Current thread:

[PATCH] Ncat as a client should quit event loop on EOF only if recvonly Tomas Hozza (Feb 07)
- Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly David Fifield (Feb 07)
  - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly Tomas Hozza (Feb 08)
    - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly David Fifield (Feb 09)
    - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly Tomas Hozza (Feb 11)
  - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly Tomas Hozza (Feb 08)
    - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly David Fifield (Feb 09)
    - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly Tomas Hozza (Feb 18)
    - Re: [PATCH] Ncat as a client should quit event loop on EOF only if recvonly David Fifield (Feb 22)