Update HTML documentation from man pages

This commit is contained in:
github-actions[bot] committed 2026-08-22 11:28:42 +00:00
1 parent 22c7dfe0e1
commit 984366ce3e
13 files changed
+719 -742

No files matched your search

+28 -28
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -25,7 +25,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b> -
<p style="margin-left:9%; margin-top: 1em"><b>3proxy</b> -
3[APA3A] tiny proxy server, or trivial proxy server, or free
proxy server</p>
@@ -34,7 +34,7 @@ proxy server</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b>
<p style="margin-left:9%; margin-top: 1em"><b>3proxy</b>
[<i>config_file</i>] <b><br>
3proxy</b> [<i>--install</i>] <b><br>
3proxy</b> [<i>--remove</i>]</p>
@@ -44,7 +44,7 @@ proxy server</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b> is
<p style="margin-left:9%; margin-top: 1em"><b>3proxy</b> is
a universal proxy server. It can be used to provide internal
users with fully controllable access to external resources
or to provide external users with access to internal
@@ -71,7 +71,7 @@ under Unix). So you can play your favourite games, listen to
music, exchange files and messages and even accept incoming
connections behind a proxy server.</p>
<p style="margin-left:6%; margin-top: 1em"><i>dnspr</i>
<p style="margin-left:9%; margin-top: 1em"><i>dnspr</i>
does not exist as an independent service. It&rsquo;s a DNS
caching proxy (it requires <i>nscache</i> and <i>nserver</i>
to be set in the configuration. Only A-records are cached.
@@ -79,7 +79,7 @@ Please note that this caching is mostly a &rsquo;hack&rsquo;
and has nothing to do with a real DNS server, but it works
perfectly for SOHO networks.</p>
<p style="margin-left:6%; margin-top: 1em">3proxy supports
<p style="margin-left:9%; margin-top: 1em">3proxy supports
access control lists (ACL) like network router. Source and
destination networks and destination port can be specified.
In addition, usernames and gateway action (for example GET
@@ -92,7 +92,7 @@ ACL action request can be allowed, denied or redirected to
another host or to another proxy server or even to a chain
of proxy servers.</p>
<p style="margin-left:6%; margin-top: 1em">It supports
<p style="margin-left:9%; margin-top: 1em">It supports
different types of logging: to logfiles, <b>syslog</b>(3)
(only under Unix) or to an ODBC database. Logging format is
tunable to provide compatibility with existing log file
@@ -105,9 +105,9 @@ Apache or Squid log parsers.</p>
<p style="margin-left:6%; margin-top: 1em"><b>config_file</b></p>
<p style="margin-left:9%; margin-top: 1em"><b>config_file</b></p>
<p style="margin-left:15%;">Name of config file. See
<p style="margin-left:18%;">Name of config file. See
<b>3proxy.cfg</b>(3) for configuration file format. Under
Windows, if config_file is not specified, <b>3proxy</b>
looks for a file named <i>3proxy.cfg</i> in the default
@@ -119,14 +119,14 @@ script just by setting +x mode and adding <br>
#!/usr/local/3proxy/3proxy <br>
as a first line in 3proxy.cfg</p>
<p style="margin-left:6%;"><b>--install</b></p>
<p style="margin-left:9%;"><b>--install</b></p>
<p style="margin-left:15%;">(Windows NT family only)
<p style="margin-left:18%;">(Windows NT family only)
install <b>3proxy</b> as a system service</p>
<p style="margin-left:6%;"><b>--remove</b></p>
<p style="margin-left:9%;"><b>--remove</b></p>
<p style="margin-left:15%;">(Windows NT family only) remove
<p style="margin-left:18%;">(Windows NT family only) remove
<b>3proxy</b> from system services</p>
<h2>SIGNALS
@@ -134,29 +134,29 @@ install <b>3proxy</b> as a system service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Under Unix there
<p style="margin-left:9%; margin-top: 1em">Under Unix there
are a few signals <b>3proxy</b> catches. See <b>kill</b>(1).
<b><br>
SIGTERM</b></p>
<p style="margin-left:15%;">clean up connections and
<p style="margin-left:18%;">clean up connections and
exit</p>
<p style="margin-left:6%;"><b>SIGPAUSE</b></p>
<p style="margin-left:9%;"><b>SIGPAUSE</b></p>
<p style="margin-left:15%;">stop accepting new connections,
<p style="margin-left:18%;">stop accepting new connections,
on second signal - start and re-read configuration</p>
<p style="margin-left:6%;"><b>SIGCONT</b></p>
<p style="margin-left:9%;"><b>SIGCONT</b></p>
<p style="margin-left:15%;">start to accept new
<p style="margin-left:18%;">start to accept new
connections</p>
<p style="margin-left:6%;"><b>SIGUSR1</b></p>
<p style="margin-left:9%;"><b>SIGUSR1</b></p>
<p style="margin-left:15%;">reload configuration</p>
<p style="margin-left:18%;">reload configuration</p>
<p style="margin-left:6%; margin-top: 1em">Under Windows,
<p style="margin-left:9%; margin-top: 1em">Under Windows,
if <b>3proxy</b> is installed as a service you can use
standard service management to start, stop, pause and
continue the 3proxy service, for example: <b><br>
@@ -165,7 +165,7 @@ net stop 3proxy <br>
net pause 3proxy <br>
net continue 3proxy</b></p>
<p style="margin-left:6%; margin-top: 1em">Web admin
<p style="margin-left:9%; margin-top: 1em">Web admin
service can also be used to reload configuration. Use wget
to automate this task.</p>
@@ -175,10 +175,10 @@ to automate this task.</p>
<p style="margin-left:6%; margin-top: 1em"><i>/usr/local/3proxy/3proxy.cfg
<p style="margin-left:9%; margin-top: 1em"><i>/usr/local/3proxy/3proxy.cfg
(3proxy.cfg)</i></p>
<p style="margin-left:15%;"><b>3proxy</b> configuration
<p style="margin-left:18%;"><b>3proxy</b> configuration
file</p>
<h2>BUGS
@@ -186,7 +186,7 @@ file</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -194,7 +194,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy.cfg(5),
<p style="margin-left:9%; margin-top: 1em">3proxy.cfg(5),
proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), tcppm(8),
udppm(8), kill(1), syslogd(8), <br>
https://3proxy.org/</p>
@@ -204,7 +204,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+27 -27
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -26,7 +26,7 @@
<p style="margin-left:6%; margin-top: 1em"><b>3proxy_crypt</b>
<p style="margin-left:9%; margin-top: 1em"><b>3proxy_crypt</b>
- utility to generate encrypted passwords for 3proxy</p>
<h2>SYNOPSIS
@@ -35,7 +35,7 @@
<p style="margin-left:6%; margin-top: 1em"><b>3proxy_crypt</b>
<p style="margin-left:9%; margin-top: 1em"><b>3proxy_crypt</b>
<i>password</i> <b><br>
3proxy_crypt</b> <i>salt password</i></p>
@@ -45,23 +45,23 @@
<p style="margin-left:6%; margin-top: 1em"><i><b>3proxy_crypt</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>3proxy_crypt</b></i>
is a utility to generate encrypted password hashes for use
with 3proxy configuration. Encrypted passwords allow the
system to avoid storing passwords in cleartext in
configuration files.</p>
<p style="margin-left:6%; margin-top: 1em">When invoked
<p style="margin-left:9%; margin-top: 1em">When invoked
with a single argument, it produces an NT password hash
(MD4-based, suitable for NTLM authentication). The output is
prefixed with <b>NT:</b>.</p>
<p style="margin-left:6%; margin-top: 1em">When invoked
<p style="margin-left:9%; margin-top: 1em">When invoked
with two arguments (salt and password), it produces a
BLAKE2b password hash. The salt length is limited to 64
characters. The output is prefixed with <b>CR:</b>.</p>
<p style="margin-left:6%; margin-top: 1em">The resulting
<p style="margin-left:9%; margin-top: 1em">The resulting
hash can be used in the 3proxy configuration file with the
<b>users</b> directive instead of a cleartext password.</p>
@@ -71,25 +71,25 @@ hash can be used in the 3proxy configuration file with the
<p style="margin-left:6%; margin-top: 1em"><i>password</i></p>
<p style="margin-left:9%; margin-top: 1em"><i>password</i></p>
<p style="margin-left:15%;">Cleartext password to
<p style="margin-left:18%;">Cleartext password to
encrypt.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="5%">
<p><i>salt</i></p></td>
<td width="4%"></td>
<td width="65%">
<td width="67%">
<p>Salt string for BLAKE2b hashing (max 64 characters).</p></td>
<td width="20%">
<td width="15%">
</td></tr>
</table>
@@ -98,30 +98,30 @@ encrypt.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Generate NT
<p style="margin-left:9%; margin-top: 1em">Generate NT
password hash:</p>
<p style="margin-left:15%;">3proxy_crypt
<p style="margin-left:18%;">3proxy_crypt
MySecretPassword</p>
<p style="margin-left:6%;">Result:</p>
<p style="margin-left:9%;">Result:</p>
<p style="margin-left:15%;">NT:3F7E6D8D96E8E7A9B0C1D2E3F4A5B6C7</p>
<p style="margin-left:18%;">NT:3F7E6D8D96E8E7A9B0C1D2E3F4A5B6C7</p>
<p style="margin-left:6%;">Generate BLAKE2b password hash
<p style="margin-left:9%;">Generate BLAKE2b password hash
with salt:</p>
<p style="margin-left:15%;">3proxy_crypt MySalt
<p style="margin-left:18%;">3proxy_crypt MySalt
MySecretPassword</p>
<p style="margin-left:6%;">Result:</p>
<p style="margin-left:9%;">Result:</p>
<p style="margin-left:15%;">CR:$3$MySalt$...</p>
<p style="margin-left:18%;">CR:$3$MySalt$...</p>
<p style="margin-left:6%;">Using in 3proxy.cfg:</p>
<p style="margin-left:9%;">Using in 3proxy.cfg:</p>
<p style="margin-left:15%;">users
<p style="margin-left:18%;">users
user1:CR:$3$MySalt$...</p>
<h2>NOTES
@@ -129,11 +129,11 @@ user1:CR:$3$MySalt$...</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">The NT hash uses
<p style="margin-left:9%; margin-top: 1em">The NT hash uses
the RSA MD4 Message-Digest Algorithm. The BLAKE2b hash uses
the BLAKE2 cryptographic hash function.</p>
<p style="margin-left:6%; margin-top: 1em">When a password
<p style="margin-left:9%; margin-top: 1em">When a password
hash is prefixed with <b>NT:</b> or <b>CR:</b>, 3proxy uses
the corresponding algorithm to verify passwords instead of
comparing cleartext strings.</p>
@@ -143,7 +143,7 @@ comparing cleartext strings.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -151,7 +151,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
3proxy.cfg(5), <br>
https://3proxy.org/</p>
@@ -160,7 +160,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+59 -61
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b> -
<p style="margin-left:9%; margin-top: 1em"><b>ftppr</b> -
FTP proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ FTP proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b>
<p style="margin-left:9%; margin-top: 1em"><b>ftppr</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]
@@ -43,7 +43,7 @@ FTP proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b> is
<p style="margin-left:9%; margin-top: 1em"><b>ftppr</b> is
FTP gateway service to allow internal users to access
external FTP servers.</p>
@@ -55,81 +55,80 @@ external FTP servers.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never look for username
authentication.</p> </td></tr>
<p>Never look for username authentication.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -140,13 +139,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -156,56 +155,55 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/ftppr.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-h</b></p></td>
<p><b>-h</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Default destination. It&rsquo;s
used if the target address is not specified by the user.</p></td></tr>
<p>Default destination. It&rsquo;s used if the target
address is not specified by the user.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 21.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 21.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -213,7 +211,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You can use any
<p style="margin-left:9%; margin-top: 1em">You can use any
FTP client, regardless of FTP proxy support. For a client
with FTP proxy support, configure <i>internal_ip</i> and
<i>port</i> in the FTP proxy parameters. For clients without
@@ -232,7 +230,7 @@ supported.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -240,7 +238,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
proxy(8), pop3p(8), socks(8), tcppm(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -250,7 +248,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+65 -67
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>imapp</b> -
<p style="margin-left:9%; margin-top: 1em"><b>imapp</b> -
IMAPv4 proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ IMAPv4 proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>imapp</b>
<p style="margin-left:9%; margin-top: 1em"><b>imapp</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]
@@ -44,7 +44,7 @@ IMAPv4 proxy gateway service</p>
<p style="margin-left:6%; margin-top: 1em"><i><b>imapp</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>imapp</b></i>
is IMAPv4 (IMAP4rev1) gateway service to allow internal
users to access external IMAP servers.</p>
@@ -56,81 +56,80 @@ users to access external IMAP servers.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never look for username
authentication.</p> </td></tr>
<p>Never look for username authentication.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -141,13 +140,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -157,69 +156,68 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/imapp.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 143.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 143.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-h</b></p></td>
<p><b>-h</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Default destination. It&rsquo;s
used if the target address is not specified by the user.</p></td></tr>
<p>Default destination. It&rsquo;s used if the target
address is not specified by the user.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-x</b></p></td>
<p><b>-x</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Disable STARTTLS support.
STARTTLS is not announced in the CAPABILITY response and the
STARTTLS command is not accepted.</p></td></tr>
<p>Disable STARTTLS support. STARTTLS is not announced in
the CAPABILITY response and the STARTTLS command is not
accepted.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -227,7 +225,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You can use any
<p style="margin-left:9%; margin-top: 1em">You can use any
MUA (Mail User Agent) with IMAPv4 support. Set the client to
use <i>internal_ip</i> and <i>port</i> as an IMAP server.
The address of the real IMAP server must be configured as a
@@ -262,7 +260,7 @@ fails.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -270,7 +268,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
ftppr(8), pop3p(8), proxy(8), smtpp(8), socks(8), tcppm(8),
tlspr(8), udppm(8), syslogd(8), <br>
https://3proxy.org/</p>
@@ -280,7 +278,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+65 -67
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>pop3p</b> -
<p style="margin-left:9%; margin-top: 1em"><b>pop3p</b> -
POP3 proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ POP3 proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>pop3p</b>
<p style="margin-left:9%; margin-top: 1em"><b>pop3p</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]
@@ -44,7 +44,7 @@ POP3 proxy gateway service</p>
<p style="margin-left:6%; margin-top: 1em"><i><b>pop3p</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>pop3p</b></i>
is POP3 gateway service to allow internal users to access
external POP3 servers.</p>
@@ -56,81 +56,80 @@ external POP3 servers.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never look for username
authentication.</p> </td></tr>
<p>Never look for username authentication.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -141,13 +140,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -157,69 +156,68 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/pop3p.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 110.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 110.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-h</b></p></td>
<p><b>-h</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Default destination. It&rsquo;s
used if the target address is not specified by the user.</p></td></tr>
<p>Default destination. It&rsquo;s used if the target
address is not specified by the user.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-x</b></p></td>
<p><b>-x</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Disable STARTTLS (STLS) support.
STLS is not announced in the CAPA response and the STLS
command is not accepted.</p></td></tr>
<p>Disable STARTTLS (STLS) support. STLS is not announced
in the CAPA response and the STLS command is not
accepted.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -227,7 +225,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You can use any
<p style="margin-left:9%; margin-top: 1em">You can use any
MUA (Mail User Agent) with POP3 support. Set the client to
use <i>internal_ip</i> and <i>port</i> as a POP3 server. The
address of the real POP3 server must be configured as a part
@@ -255,7 +253,7 @@ TLS handshake with the client fails.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -263,7 +261,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -273,7 +271,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+62 -66
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b> -
<p style="margin-left:9%; margin-top: 1em"><b>proxy</b> -
HTTP proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ HTTP proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b>
<p style="margin-left:9%; margin-top: 1em"><b>proxy</b>
[<b>-d</b>][<b>-a</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]</p>
@@ -42,7 +42,7 @@ HTTP proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b> is
<p style="margin-left:9%; margin-top: 1em"><b>proxy</b> is
HTTP gateway service with HTTPS and FTP over HTTPS
support.</p>
@@ -54,81 +54,80 @@ support.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never ask for username
authentication</p> </td></tr>
<p>Never ask for username authentication</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -139,13 +138,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p><b>-i</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -155,68 +154,65 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/proxy.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-a</b></p></td>
<p><b>-a</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Anonymous. Hide information
about client.</p></td></tr>
<p>Anonymous. Hide information about client.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-a1</b></p></td>
<p><b>-a1</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Anonymous. Show fake information
about client.</p></td></tr>
<p>Anonymous. Show fake information about client.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 3128.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 3128.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; preceeds
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; preceeds <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -224,7 +220,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You should use a
<p style="margin-left:9%; margin-top: 1em">You should use a
client with HTTP proxy support or configure a router to
redirect HTTP traffic to the proxy (transparent proxy).
Configure the client to connect to <i>internal_ip</i> and
@@ -237,7 +233,7 @@ TCP-based protocol. If you need to limit clients, use
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -245,7 +241,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -255,7 +251,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+65 -67
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>smtpp</b> -
<p style="margin-left:9%; margin-top: 1em"><b>smtpp</b> -
SMTP proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ SMTP proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>smtpp</b>
<p style="margin-left:9%; margin-top: 1em"><b>smtpp</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]
@@ -44,7 +44,7 @@ SMTP proxy gateway service</p>
<p style="margin-left:6%; margin-top: 1em"><i><b>smtpp</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>smtpp</b></i>
is SMTP gateway service to allow internal users to access
external SMTP servers.</p>
@@ -56,81 +56,80 @@ external SMTP servers.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never look for username
authentication.</p> </td></tr>
<p>Never look for username authentication.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -141,13 +140,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -157,69 +156,68 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/smtpp.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 587.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 587.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-h</b></p></td>
<p><b>-h</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Default destination. It&rsquo;s
used if the target address is not specified by the user.</p></td></tr>
<p>Default destination. It&rsquo;s used if the target
address is not specified by the user.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-x</b></p></td>
<p><b>-x</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Disable STARTTLS support.
STARTTLS is not announced in the EHLO response and the
STARTTLS command is not accepted.</p></td></tr>
<p>Disable STARTTLS support. STARTTLS is not announced in
the EHLO response and the STARTTLS command is not
accepted.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -227,7 +225,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You can use any
<p style="margin-left:9%; margin-top: 1em">You can use any
MUA (Mail User Agent) with SMTP authentication support. Set
the client to use <i>internal_ip</i> and <i>port</i> as an
SMTP server. The address of the real SMTP server must be
@@ -256,7 +254,7 @@ fails.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -264,7 +262,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -274,7 +272,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+73 -76
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>socks</b> -
<p style="margin-left:9%; margin-top: 1em"><b>socks</b> -
SOCKS 4/4.5/5 gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ SOCKS 4/4.5/5 gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>socks</b>
<p style="margin-left:9%; margin-top: 1em"><b>socks</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
[<b>-e</b><i>external_ip</i>]</p>
@@ -42,7 +42,7 @@ SOCKS 4/4.5/5 gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>socks</b> is
<p style="margin-left:9%; margin-top: 1em"><b>socks</b> is
SOCKS server. It supports SOCKSv4, SOCKSv4.5 (extension to
v4 for server side name resolution) and SOCKSv5. SOCKSv5
specification allows both outgoing and reverse TCP
@@ -56,82 +56,81 @@ connections and UDP portmapping.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never ask for username
authentication</p> </td></tr>
<p>Never ask for username authentication</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from.
External IP must be specified if you need incoming
connections. By default, the system will decide which
address to use in accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. External IP must be
specified if you need incoming connections. By default, the
system will decide which address to use in accordance with
the routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -142,13 +141,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p><b>-Ne</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p>External NAT address 3proxy reports to client for
@@ -157,77 +156,75 @@ and destination server. By default, the external address is
reported. It&rsquo;s only useful in the case of IP-IP NAT
and does not work with port translation.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-Ni</b></p></td>
<p><b>-Ni</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Internal NAT address 3proxy
reports to client for UDPASSOC. This is external address of
the NAT between 3proxy and the client, client uses to
connect to 3proxy. By default, the internal address is
reported. It&rsquo;s only useful in the case of IP-IP NAT
and does not work with port translation.</p></td></tr>
<p>Internal NAT address 3proxy reports to client for
UDPASSOC. This is external address of the NAT between 3proxy
and the client, client uses to connect to 3proxy. By
default, the internal address is reported. It&rsquo;s only
useful in the case of IP-IP NAT and does not work with port
translation.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-i</b></p></td>
<p><b>-i</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Internal address. IP address the
proxy accepts connections to. By default, connections to any
interface are accepted. It&acute;s usually unsafe. Unix
domain sockets can be specified with
<i>-iunix:/path/to/socket</i> syntax (e.g.,
-iunix:/var/run/socks.sock). On Linux, abstract sockets use
<i>-iunix:@socketname</i> syntax.</p></td></tr>
<p>Internal address. IP address the proxy accepts
connections to. By default, connections to any interface are
accepted. It&acute;s usually unsafe. Unix domain sockets can
be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/socks.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Port. Port proxy listens for
incoming connections. Default is 1080.</p></td></tr>
<p>Port. Port proxy listens for incoming connections.
Default is 1080.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; preceeds
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; preceeds <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -235,7 +232,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You should use a
<p style="margin-left:9%; margin-top: 1em">You should use a
client with SOCKS support or use some socksification support
(for example <i>SocksCAP</i> or <i>FreeCAP</i>). Configure
client to use <i>internal_ip</i> and <i>port</i>. SOCKS
@@ -250,7 +247,7 @@ privileges). If you need to control access, use
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -258,7 +255,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
proxy(8), ftppr(8), pop3p(8), tcppm(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -268,7 +265,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+51 -52
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -25,7 +25,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>tcppm</b> -
<p style="margin-left:9%; margin-top: 1em"><b>tcppm</b> -
TCP port mapper</p>
<h2>SYNOPSIS
@@ -33,7 +33,7 @@ TCP port mapper</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>tcppm</b>
<p style="margin-left:9%; margin-top: 1em"><b>tcppm</b>
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-i</b><i>internal_ip</i>] [<b>-e</b><i>external_ip</i>]
<i>local_port remote_host remote_port</i></p>
@@ -44,7 +44,7 @@ TCP port mapper</p>
<p style="margin-left:6%; margin-top: 1em"><i><b>tcppm</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>tcppm</b></i>
forwards connections from local to remote TCP port</p>
<h2>OPTIONS
@@ -55,69 +55,69 @@ forwards connections from local to remote TCP port</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -128,13 +128,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -144,32 +144,31 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/tcppm.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>ARGUMENTS
@@ -178,23 +177,23 @@ You may want to try something like -S8192 if you experience
<p style="margin-left:6%; margin-top: 1em"><i>local_port</i></p>
<p style="margin-left:9%; margin-top: 1em"><i>local_port</i></p>
<p style="margin-left:15%;">- port tcppm accepts
<p style="margin-left:18%;">- port tcppm accepts
connections on</p>
<p style="margin-left:6%;"><i>remote_host</i></p>
<p style="margin-left:9%;"><i>remote_host</i></p>
<p style="margin-left:15%;">- IP address of the host the
<p style="margin-left:18%;">- IP address of the host the
connection is forwarded to. Unix domain sockets can be
specified with the syntax <i>unix:/path/to/socket</i> (e.g.,
unix:/var/run/app.sock). On Linux, abstract (fileless) Unix
sockets use the syntax <i>unix:@socketname</i> (e.g.,
unix:@app.socket).</p>
<p style="margin-left:6%;"><i>remote_port</i></p>
<p style="margin-left:9%;"><i>remote_port</i></p>
<p style="margin-left:15%;">- remote port the connection is
<p style="margin-left:18%;">- remote port the connection is
forwarded to. Ignored when using Unix socket destination,
but must be specified (use any positive value) for syntax
compatibility.</p>
@@ -204,7 +203,7 @@ compatibility.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Any TCP-based
<p style="margin-left:9%; margin-top: 1em">Any TCP-based
application can be used as a client. Use <i>internal_ip</i>
and <i>local_port</i> as the destination in the client
application. The connection is forwarded to
@@ -215,7 +214,7 @@ application. The connection is forwarded to
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -223,7 +222,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -233,7 +232,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+83 -88
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -24,7 +24,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> -
<p style="margin-left:9%; margin-top: 1em"><b>tlspr</b> -
SNI proxy gateway service</p>
<h2>SYNOPSIS
@@ -32,7 +32,7 @@ SNI proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b>
<p style="margin-left:9%; margin-top: 1em"><b>tlspr</b>
[<b>-d</b>][<b>-a</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-p</b><i>listening_port</i>]
[<b>-P</b><i>destination_port</i>]
@@ -45,7 +45,7 @@ SNI proxy gateway service</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> is
<p style="margin-left:9%; margin-top: 1em"><b>tlspr</b> is
an SNI gateway service (destination host is taken from TLS
handshake). The destination port must be specified via the
-P option (or it may be detected with the Transparent
@@ -61,81 +61,80 @@ access control is required.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-u</b></p></td>
<p><b>-u</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Never ask for username
authentication</p> </td></tr>
<p>Never ask for username authentication</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate connections from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate connections from. By default, the system
will decide which address to use in accordance with the
routing table.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -146,13 +145,13 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p><b>-i</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts
@@ -162,93 +161,90 @@ be specified with <i>-iunix:/path/to/socket</i> syntax
(e.g., -iunix:/var/run/tlspr.sock). On Linux, abstract
sockets use <i>-iunix:@socketname</i> syntax.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-a</b></p></td>
<p><b>-a</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Anonymous. Hide information
about client.</p></td></tr>
<p>Anonymous. Hide information about client.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-a1</b></p></td>
<p><b>-a1</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Anonymous. Show fake information
about client.</p></td></tr>
<p>Anonymous. Show fake information about client.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-p</b></p></td>
<p><b>-p</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">listening_port. Port proxy
listens for incoming connections. Default is 1443.</p></td></tr>
<p>listening_port. Port proxy listens for incoming
connections. Default is 1443.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-P</b></p></td>
<p><b>-P</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">destination_port. Port to
establish outgoing connections. Required unless the
Transparent plugin is used, because the TLS handshake does
not contain port information. Default is 443.</p></td></tr>
<p>destination_port. Port to establish outgoing
connections. Required unless the Transparent plugin is used,
because the TLS handshake does not contain port information.
Default is 443.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-c</b></p></td>
<p><b>-c</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">TLS_CHECK_LEVEL. 0 (default) -
allow non-TLS traffic to pass, 1 - require TLS, only check
client HELLO packet, 2 - require TLS, check both client and
server HELLO, 3 - require TLS, check that the server sends a
certificate (not compatible with TLS 1.3), 4 - require
mutual TLS, check that the server sends a certificate
request and the client sends a certificate (not compatible
with TLS 1.3)</p></td></tr>
<p>TLS_CHECK_LEVEL. 0 (default) - allow non-TLS traffic to
pass, 1 - require TLS, only check client HELLO packet, 2 -
require TLS, check both client and server HELLO, 3 - require
TLS, check that the server sends a certificate (not
compatible with TLS 1.3), 4 - require mutual TLS, check that
the server sends a certificate request and the client sends
a certificate (not compatible with TLS 1.3)</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="4%">
<p style="margin-top: 1em"><b>-s</b></p></td>
<p><b>-s</b></p></td>
<td width="5%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Split the TLS Client HELLO
packet across multiple TCP segments to make SNI-based DPI
detection harder. An optional numeric value can follow (e.g.
<b>-s1</b>) to control the splitting behaviour.</p></td></tr>
<p>Split the TLS Client HELLO packet across multiple TCP
segments to make SNI-based DPI detection harder. An optional
numeric value can follow (e.g. <b>-s1</b>) to control the
splitting behaviour.</p></td></tr>
</table>
<p style="margin-left:6%;"><b>-Ximap | -Xpop3 |
<p style="margin-left:9%;"><b>-Ximap | -Xpop3 |
-Xsmtp</b></p>
<p style="margin-left:15%;">STARTTLS mode for the given
<p style="margin-left:18%;">STARTTLS mode for the given
protocol. The proxy speaks the plaintext protocol with the
client (greeting, capability advertisement with STARTTLS
only, STARTTLS command), then, after the client issues
@@ -262,13 +258,13 @@ client fails.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Log. By default logging is to stdout. If <i>logfile</i>
@@ -276,18 +272,17 @@ is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>CLIENTS
@@ -295,7 +290,7 @@ You may want to try something like -S8192 if you experience
</h2>
<p style="margin-left:6%; margin-top: 1em">You should use a
<p style="margin-left:9%; margin-top: 1em">You should use a
client with TLS support or configure a router to redirect
TLS traffic to the proxy (transparent proxy). Configure the
client to connect to <i>internal_ip</i> and <i>port</i>. If
@@ -306,7 +301,7 @@ you need to limit clients, use <b>3proxy</b>(8) instead.</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -314,7 +309,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
ftppr(8), proxy(8), socks(8), pop3p(8), smtpp(8), tcppm(8),
udppm(8), syslogd(8), <br>
https://3proxy.org/</p>
@@ -324,7 +319,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>
+59 -61
View File
@@ -1,4 +1,4 @@
<!-- Creator : groff version 1.24.1 -->
<!-- Creator : groff version 1.23.0 -->
<html>
<head>
@@ -25,7 +25,7 @@
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>udppm</b> -
<p style="margin-left:9%; margin-top: 1em"><b>udppm</b> -
UDP port mapper</p>
<h2>SYNOPSIS
@@ -33,7 +33,7 @@ UDP port mapper</p>
</h2>
<p style="margin-left:6%; margin-top: 1em"><b>udppm</b>
<p style="margin-left:9%; margin-top: 1em"><b>udppm</b>
[<b>-ds</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
[<b>-i</b><i>internal_ip</i>] [<b>-e</b><i>external_ip</i>]
<i>local_port remote_host remote_port</i></p>
@@ -44,7 +44,7 @@ UDP port mapper</p>
<p style="margin-left:6%; margin-top: 1em"><i><b>udppm</b></i>
<p style="margin-left:9%; margin-top: 1em"><i><b>udppm</b></i>
forwards datagrams from local to remote UDP port</p>
<h2>OPTIONS
@@ -55,69 +55,69 @@ forwards datagrams from local to remote UDP port</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-I</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Inetd mode. Standalone service
only.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-d</b></p></td>
<p><b>-d</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Daemonize. Detach service from
console and run in the background.</p></td></tr>
<p>Daemonize. Detach service from console and run in the
background.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-t</b></p></td>
<p><b>-t</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Be silenT. Do not log
start/stop/accept error records.</p></td></tr>
<p>Be silenT. Do not log start/stop/accept error
records.</p> </td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-e</b></p></td>
<p><b>-e</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">External address. IP address of
the interface the proxy should initiate datagrams from. By
default, the system will decide which address to use in
accordance with the routing table.</p></td></tr>
<p>External address. IP address of the interface the proxy
should initiate datagrams from. By default, the system will
decide which address to use in accordance with the routing
table.</p> </td></tr>
</table>
<p style="margin-left:6%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ni</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> before opening
the listening socket. The current namespace is saved and
restored immediately after binding, so outgoing connections
run in the original namespace unless <b>-ne</b> is also
given.</p>
<p style="margin-left:6%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:9%;"><b>-ne</b><i>PATH</i></p>
<p style="margin-left:15%;">(Linux only) Switch to the
<p style="margin-left:18%;">(Linux only) Switch to the
network namespace identified by <i>PATH</i> after the
listening socket has been bound (and after restoring from
<b>-ni</b> if applicable). Both options accept any namespace
@@ -128,61 +128,59 @@ file path (e.g. <i>/var/run/netns/myns</i> or
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p><b>-i</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p>Internal address. IP address the proxy accepts datagrams
to. By default, connections to any interface are accepted.
It&acute;s usually unsafe.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-l</b></p></td>
<p><b>-l</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Log. By default logging is to
stdout. If <i>logfile</i> is specified logging is to file.
Under Unix, if &acute;<i>@</i>&acute; precedes
<i>logfile</i>, syslog is used for logging.</p></td></tr>
<p>Log. By default logging is to stdout. If <i>logfile</i>
is specified logging is to file. Under Unix, if
&acute;<i>@</i>&acute; precedes <i>logfile</i>, syslog is
used for logging.</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-s</b></p></td>
<p><b>-s</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Single packet. By default, only
one client can use the udppm service, but if -s is
specified, only one packet will be forwarded between client
and server. This allows the service to be shared between
multiple clients for single-packet services (for example,
name lookups).</p></td></tr>
<p>Single packet. By default, only one client can use the
udppm service, but if -s is specified, only one packet will
be forwarded between client and server. This allows the
service to be shared between multiple clients for
single-packet services (for example, name lookups).</p></td></tr>
<tr valign="top" align="left">
<td width="6%"></td>
<td width="9%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>-S</b></p></td>
<p><b>-S</b></p></td>
<td width="6%"></td>
<td width="85%">
<td width="82%">
<p style="margin-top: 1em">Increase or decrease stack size.
You may want to try something like -S8192 if you experience
3proxy crashes.</p></td></tr>
<p>Increase or decrease stack size. You may want to try
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
</table>
<h2>ARGUMENTS
@@ -191,19 +189,19 @@ You may want to try something like -S8192 if you experience
<p style="margin-left:6%; margin-top: 1em"><i>local_port</i></p>
<p style="margin-left:9%; margin-top: 1em"><i>local_port</i></p>
<p style="margin-left:15%;">- port udppm accepts datagrams
<p style="margin-left:18%;">- port udppm accepts datagrams
on</p>
<p style="margin-left:6%;"><i>remote_host</i></p>
<p style="margin-left:9%;"><i>remote_host</i></p>
<p style="margin-left:15%;">- IP address of the host
<p style="margin-left:18%;">- IP address of the host
datagrams are forwarded to</p>
<p style="margin-left:6%;"><i>remote_port</i></p>
<p style="margin-left:9%;"><i>remote_port</i></p>
<p style="margin-left:15%;">- remote port datagrams are
<p style="margin-left:18%;">- remote port datagrams are
forwarded to</p>
<h2>CLIENTS
@@ -211,7 +209,7 @@ forwarded to</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">Any UDP-based
<p style="margin-left:9%; margin-top: 1em">Any UDP-based
application can be used as a client. Use <i>internal_ip</i>
and <i>local_port</i> as the destination in the client
application. All datagrams are forwarded to
@@ -222,7 +220,7 @@ application. All datagrams are forwarded to
</h2>
<p style="margin-left:6%; margin-top: 1em">Report all bugs
<p style="margin-left:9%; margin-top: 1em">Report all bugs
to <b>3proxy@3proxy.org</b></p>
<h2>SEE ALSO
@@ -230,7 +228,7 @@ to <b>3proxy@3proxy.org</b></p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
<p style="margin-left:9%; margin-top: 1em">3proxy(8),
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
syslogd(8), <br>
https://3proxy.org/</p>
@@ -240,7 +238,7 @@ https://3proxy.org/</p>
</h2>
<p style="margin-left:6%; margin-top: 1em">3proxy is
<p style="margin-left:9%; margin-top: 1em">3proxy is
designed by Vladimir Dubrovin &lt;vlad@3proxy.org&gt;</p>
<hr>
</body>