Ncat cannot handle unnamed AF_UNIX sockets
Open
Nobody has claimed this yet.
bug
GSoC Idea
Ncat
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.9k
- PR merge metrics
- No merged PRs in 30d
Description
Definitely affects SOCK_DGRAM (--udp), but may also have impact on SOCK_STREAM (TCP-style, the default). See http://seclists.org/nmap-dev/2014/q4/343 and #23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Ncat behavior with unnamed AF_UNIX SOCK_DGRAM sockets using --udp, then check whether the default SOCK_STREAM path is affected. Read the linked nmap-dev discussion and issue #23 for expected behavior; done means Ncat handles the affected unnamed socket modes without the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100