Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncat documentation is not sufficiently covering SOCKS5 proxying #996

nnposter opened this Issue Aug 30, 2017 · 3 comments


None yet
3 participants
Copy link

nnposter commented Aug 30, 2017

The current ncat manpage-like files are not covering the SOCKS5 proxy functionality.

@dmiller-nmap Dan, I do not mind fixing the documentation but it is not clear to me which file is the master and what tools are used to produce the remaining formats. Do you have any guidance?


This comment has been minimized.

Copy link

dmiller-nmap commented Sep 6, 2017

The xml files are the source, written in DocBook XML. Any edits will be reflected in the nroff man pages when those are updated, usually around release time.


This comment has been minimized.

Copy link

fyodor commented Sep 14, 2017

@nnposter -- great catch about SOCKS5. Yeah, if you could add that, it would be great. The Ncat man page is generated from ncat/docs/ncat.xml. Sometimes installing DocBook and such is a pain, so if you just update ncat.xml, we can regenerate the HTML and Nroff versions later. Cheers!


This comment has been minimized.

Copy link

nnposter commented Sep 14, 2017

Sure. Changes are actually needed in both ncat.xml and ncatguide.xml. I have already put the patch together over the last weekend and I plan to commit it sometime next week (together with my other outstanding patches).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.