Bug 826601 - ncat does not write to output file with UDP
Summary: ncat does not write to output file with UDP
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nmap
Version: 6.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Hubert Kario
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-30 15:11 UTC by Patrik Kis
Modified: 2013-05-30 15:49 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-05-30 15:49:21 UTC


Attachments (Terms of Use)
patch to fix this (1011 bytes, patch)
2012-06-19 09:03 UTC, Michal Hlavinka
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0881 normal SHIPPED_LIVE nmap bug fix update 2013-05-30 19:48:16 UTC

Description Patrik Kis 2012-05-30 15:11:10 UTC
Description of problem:
ncat does not write the session data to output file when the protocol is UDP

Version-Release number of selected component (if applicable):
nmap-5.51-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
# ncat --udp --output ncatudp.log --listen 6666
TEST
^C
# ls -l ncatudp.log
-rw-r--r--. 1 root root 0 May 30 18:06 ncatudp.log

In this test the following command was used to send data to the server:
# echo TEST | ncat --udp localhost 6666
 
Actual results:
the output file is empty

Expected results:
# ncat --output ncattcp.log --listen 6666
TEST
^C
# cat ncattcp.log 
TEST

Comment 2 Michal Hlavinka 2012-06-05 10:20:35 UTC
reproducible in both rhel and latest fedora

Comment 4 Michal Hlavinka 2012-06-19 09:03:17 UTC
Created attachment 592879 [details]
patch to fix this

Comment 11 errata-xmlrpc 2013-05-30 15:49:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0881.html


Note You need to log in before you can comment on or make changes to this bug.