mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-09 09:27:59 +00:00
Man page for psocks.
This commit is contained in:
parent
7d1aae13c7
commit
f039e5f453
@ -60,7 +60,7 @@ putty.info: $(INPUTS)
|
||||
|
||||
MKMAN = $(HALIBUT) --man=$@ mancfg.but $<
|
||||
MANPAGES = putty.1 puttygen.1 plink.1 pscp.1 psftp.1 puttytel.1 pterm.1 \
|
||||
pageant.1 psusan.1
|
||||
pageant.1 psocks.1 psusan.1
|
||||
man: $(MANPAGES)
|
||||
|
||||
putty.1: man-putty.but mancfg.but; $(MKMAN)
|
||||
@ -71,6 +71,7 @@ psftp.1: man-psftp.but mancfg.but; $(MKMAN)
|
||||
puttytel.1: man-puttytel.but mancfg.but; $(MKMAN)
|
||||
pterm.1: man-pterm.but mancfg.but; $(MKMAN)
|
||||
pageant.1: man-pageant.but mancfg.but; $(MKMAN)
|
||||
psocks.1: man-psocks.but mancfg.but; $(MKMAN)
|
||||
psusan.1: man-psusan.but mancfg.but; $(MKMAN)
|
||||
|
||||
mostlyclean:
|
||||
|
92
doc/man-psocks.but
Normal file
92
doc/man-psocks.but
Normal file
@ -0,0 +1,92 @@
|
||||
\cfg{man-identity}{psocks}{1}{2021-04-08}{PuTTY tool suite}{PuTTY tool suite}
|
||||
|
||||
\H{psocks-manpage} Man page for \cw{psocks}
|
||||
|
||||
\S{psocks-manpage-name} NAME
|
||||
|
||||
\cw{psocks} \- simple SOCKS proxy server
|
||||
|
||||
\S{psocks-manpage-synopsis} SYNOPSIS
|
||||
|
||||
\c psocks [ -d ] [ -f | -p pipe-cmd ] [ -g ] [ port-number ]
|
||||
\e bbbbbb bb bb bb iiiiiiii bb iiiiiiiiiii
|
||||
|
||||
\S{psocks-manpage-description} DESCRIPTION
|
||||
|
||||
\cw{psocks} is a simple SOCKS4/5 proxy server. It supports proxying
|
||||
IPv4 and IPv6 connections. It does not support requiring
|
||||
authentication of its clients.
|
||||
|
||||
\cw{psocks} can be used together with an SSH client such as
|
||||
\cw{putty(1)} to implement a reverse dynamic SSH tunnel. It can also
|
||||
be used for network protocol debugging, as it can record all the
|
||||
traffic passing through it in various ways.
|
||||
|
||||
By default, \cw{psocks} listens to connections from localhost only,
|
||||
on TCP port 1080. A different \e{port-number} can optionally be
|
||||
supplied, and with \cw{-g} it will listen to connections from any
|
||||
host.
|
||||
|
||||
\cw{psocks} will emit log messages about connections it receives on
|
||||
standard error. With \cw{-d}, it will log the contents of those
|
||||
connections too.
|
||||
|
||||
\S{psocks-manpage-options} OPTIONS
|
||||
|
||||
The command-line options supported by \cw{psocks} are:
|
||||
|
||||
\dt \cw{-g}
|
||||
|
||||
\dd Accept connections from anywhere. By default, \cw{psocks} only
|
||||
accepts connections on the loopback interface.
|
||||
|
||||
\dt \cw{--exec} \e{command}
|
||||
|
||||
\dd \cw{psocks} will run the provided command as a subprocess. When
|
||||
the subprocess terminates, \cw{psocks} will terminate as well.
|
||||
|
||||
\lcont{
|
||||
|
||||
All arguments on the \cw{psocks} command line after \cw{--exec} will be
|
||||
treated as part of the command to run, even if they look like other
|
||||
valid \cw{psocks} options.
|
||||
|
||||
}
|
||||
|
||||
\dt \cw{-d}
|
||||
|
||||
\dd Log all traffic to standard error, in a more or less human-readable
|
||||
form (in addition to messages about connections being opened and
|
||||
closed, which are always logged).
|
||||
|
||||
\dt \cw{-f}
|
||||
|
||||
\dd Record all traffic to files. For every incoming connection, two
|
||||
files are created, \cw{sockout.NNNN} and \cw{sockin.NNNN}, where
|
||||
\e{NNNN} is a decimal index starting at 0 identifying the proxied
|
||||
connection. These record, respectively, traffic from the SOCKS client,
|
||||
and from the server it connected to through the proxy.
|
||||
|
||||
\dt \cw{-p} \e{pipe-cmd}
|
||||
|
||||
\dd Pipe all traffic to a command. For every incoming connection,
|
||||
\e{pipe-cmd} is invoked twice:
|
||||
|
||||
\lcont{
|
||||
\c pipe-cmd out N
|
||||
\e iiiiiiii bbb i
|
||||
\c pipe-cmd in N
|
||||
\e iiiiiiii bb i
|
||||
|
||||
Each command will run for the direction of a proxied connection, and
|
||||
have the connection's traffic piped into it, similar to \cw{-f}.
|
||||
}
|
||||
|
||||
\S{psocks-manpage-examples} EXAMPLES
|
||||
|
||||
In combination with the \e{plink(1)} SSH client, to set up a reverse
|
||||
dynamic SSH tunnel, in which the remote listening port 1080 on
|
||||
remote host \cw{myhost} acts as a SOCKS server giving access to your
|
||||
local network:
|
||||
|
||||
\c psocks 12345 --exec plink -R 1080:localhost:12345 user@myhost
|
2
psocks.c
2
psocks.c
@ -484,7 +484,7 @@ void psocks_cmdline(psocks_state *ps, int argc, char **argv)
|
||||
* subcommand, even if they look like options */
|
||||
doing_opts = false;
|
||||
} else if (!strcmp(p, "--help")) {
|
||||
printf("usage: psocks [ -d | -f");
|
||||
printf("usage: psocks [ -d ] [ -f");
|
||||
if (ps->platform->open_pipes)
|
||||
printf(" | -p pipe-cmd");
|
||||
printf(" ] [ -g ] port-number");
|
||||
|
Loading…
Reference in New Issue
Block a user