File: desproxy-socksserver.1.pod

package info (click to toggle)
desproxy 0.1.0~pre3-10.1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, sid, trixie
  • size: 436 kB
  • sloc: ansic: 1,753; makefile: 81; sh: 29
file content (60 lines) | stat: -rw-r--r-- 1,329 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
#  This is manual page in Perl POD format. Read more at
#  http://perldoc.perl.org/perlpod.html or run command:
#
#     perldoc perlpod | less
#
#  To check the syntax:
#
#     podchecker *.pod
#
#  Create manual page with command:
#
#    pod2man PAGE.N.pod > PAGE.N

=pod

=head1 NAME

desproxy-socksserver - Using desproxy with dynamic connections

=head1 SYNOPSIS

  desproxy-socksserver proxy_host proxy_port local_port

=head1 OPTIONS

None.

=head1 DESCRIPTION

You can see that for every application that needs to be un-proxyzed
you have to start a desproxy program. That is OK if you are using irc,
ssh or other application that always connects to the same server. But
if you need to dynamically establish TCP connections it's impossible
to follow that path.

That's why desproxy-socksserver, which is just a desproxy
implementation of a Socks 5 Server. A Socks 5 Server is like a "TCP
proxy": you just request a TCP connection and the Socks 5 Server does
the work for you. Of course, client applications need to have support
for Socks 5 Server.

=head1 ENVIRONMENT

None.

=head1 FILES

None.

=head1 SEE ALSO

dnsproxy(1)

=head1 AUTHORS

This manual page was written by Jari Aalto <jari.aalto@cante.net>, for
the Debian GNU system (but may be used by others). Released under
license GPL v2 or any later version.

=cut