Gecko [ www.thearyasamaj.org ]

Name	Size	Permission
ASCII.html	3.71 KB	-rw-r--r--
AWS.html	26.05 KB	-rw-r--r--
AuthFiles.html	9.54 KB	-rw-r--r--
Authentication.html	15.32 KB	-rw-r--r--
BCP.html	13.7 KB	-rw-r--r--
Chroot.html	14.27 KB	-rw-r--r--
Classes.html	5.92 KB	-rw-r--r--
Compiling.html	34.11 KB	-rw-r--r--
ConfigFile.html	16.47 KB	-rw-r--r--
ConfigurationTricks.html	16.54 KB	-rw-r--r--
ConnectionACLs.html	6.84 KB	-rw-r--r--
Controls.html	11.95 KB	-rw-r--r--
CreateHome.html	7.79 KB	-rw-r--r--
DNS.html	6.92 KB	-rw-r--r--
DSO.html	14.9 KB	-rw-r--r--
Debugging.html	12.47 KB	-rw-r--r--
Directory.html	10.89 KB	-rw-r--r--
DisplayFiles.html	6.69 KB	-rw-r--r--
ECCN.html	4.73 KB	-rw-r--r--
FTP.html	16.09 KB	-rw-r--r--
FXP.html	5.57 KB	-rw-r--r--
Filters.html	7.93 KB	-rw-r--r--
Globbing.html	5.53 KB	-rw-r--r--
KeepAlives.html	19.68 KB	-rw-r--r--
Limit.html	15.08 KB	-rw-r--r--
ListOptions.html	6.18 KB	-rw-r--r--
LogLevels.html	5.08 KB	-rw-r--r--
LogMessages.html	14.89 KB	-rw-r--r--
Logging.html	22.37 KB	-rw-r--r--
Memcache.html	9.04 KB	-rw-r--r--
NAT.html	11.15 KB	-rw-r--r--
Nonroot.html	4.23 KB	-rw-r--r--
Quotas.html	17.17 KB	-rw-r--r--
Radius.html	17.35 KB	-rw-r--r--
Redis.html	8.53 KB	-rw-r--r--
Regex.html	22.23 KB	-rw-r--r--
Rewrite.html	16.8 KB	-rw-r--r--
SQL.html	40.55 KB	-rw-r--r--
SSH.html	5.14 KB	-rw-r--r--
Scoreboard.html	9.11 KB	-rw-r--r--
Sendfile.html	7.34 KB	-rw-r--r--
ServerType.html	10.45 KB	-rw-r--r--
Stopping.html	10.31 KB	-rw-r--r--
TLS.html	58.93 KB	-rw-r--r--
Testing.html	8.73 KB	-rw-r--r--
Timestamps.html	6.71 KB	-rw-r--r--
Tracing.html	8.68 KB	-rw-r--r--
Translations.html	3.52 KB	-rw-r--r--
Umask.html	9.16 KB	-rw-r--r--
Upgrade.html	2.14 KB	-rw-r--r--
Versioning.html	5.41 KB	-rw-r--r--
Vhost.html	11.55 KB	-rw-r--r--
VirtualUsers.html	8.8 KB	-rw-r--r--
ftpaccess.html	2.03 KB	-rw-r--r--
index.html	10.45 KB	-rw-r--r--

Code Editor : SSH.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD: Configuring FTP over SSH</title>
</head>

<hr>
<center><h2>ProFTPD: Configuring FTP over SSH</h2></center>
<hr>
IMPORTANT NOTICE: the original instructions listed on this page,
based on <a href="http://www.proftpd.org/proftpd-l-archive/98-11/msg00066.html">http://www.proftpd.org/proftpd-l-archive/98-11/msg00066.html</a> were
incorrect, and did not lead to the proper encryption of the FTP control
channel. Many, many thanks to Michael Jochimsen for pointing out the
incorrect use of ssh port forwarding! 
<hr>

Premise 
The File Transfer Protocol is an old protocol, and like many of the older
protocols it was developed in a time when security was not of such a paramount
concern. One aspect of FTP that reflects this is the transmission of
passwords, used to prove to the server that the client is who they say they
are, &quot;in the clear&quot;, unencrypted, visible to any packet sniffer.
Protocols like SSH, and its <code>scp</code> program, are replacing FTP
as a means to securely transfer files among hosts.

However, many people still prefer to use their standard FTP clients. What
would be easiest would be a way to allow such clients to function while
transparently providing the encryption necessary for today's networks. Can
this be done? Yes - after a fashion. This document aims to describe how
to tunnel FTP over an SSH channel, providing for secure transmission of
the user's password.

Client Configuration 
The trick to encrypting the password is to make use of ssh's local port
forwarding capability. It works by creating a sort of proxy on the local host
that listens to some high-numbered port. Any traffic sent to that port
is encrypted, and forwarded to the configured remote address and port.
(Note: the prior instructions' flaw was that the local port forwarding
request was sent to localhost, rather than to the remote server, which
effectively set up the encrypted channel between localhost and itself).
Here's how to set up a local port forward:
<pre>
 $ ssh -Llocal-port:remote-addr:remote-port user@host
</pre>
This says to listen on port local-port on localhost, and to send that
encrypted traffic to host's remote-addr at port
remote-port. To use this trick to secure an FTP session (to be
specific, the control channel, through which passwords are transmitted, will
be encrypted; the data channel will not), it would look like:
<pre>
 $ ssh -f -L3000:ftpserver:21 ftpserver 'exec sleep 10' &amp;&amp; ftp localhost 3000
</pre>
Note that the choice of local-port is arbitrary. Using port
<code>3000</code> is not a requirement. This trick also requires that
the ftp client use passive mode data transfers, so make sure to use a client
that understands FTP passive mode.

Remember that only the control connection is encrypted, not the data
connection: any data you transfer (e.g. directory listings, files
uploaded or downloaded) are still sent &quot;in the clear&quot;. Your
password (and the other FTP commands sent by the client) is not.

Server Configuration 
The server side of the connection needs some configuration to make the ssh
tunneling work as well. First, the client need a valid account on the remote
host is necessary in order to support the ssh tunnel. A valid shell is not
strictly necessary for these ssh tunnels, though; something like:
<pre>
 #!/bin/sh
 sleep 10
</pre>
would suffice. This would prevent the FTP users from logging in, yet give them
enough time to establish a port forwarded ssh connection. With this sort
of quasi-shell (although, strictly speaking, there are better, more restrictive
shells than this example, as it could be escaped from), one can ssh over any
command:
<pre>
 $ ssh -l test -f -L3000:ftpserver:21 ftpserver true &amp;&amp; ftp localhost 3000
</pre>
You'll also need to use the
<a href="../modules/mod_core.html#AllowForeignAddress"><code>AllowForeignAddress</code></a> configuration directive in your
configuration file:
<pre>
 AllowForeignAddress on
</pre>
or <code>proftpd</code> will reject the passive transfer connections and log:
<pre>
 SECURITY VIOLATION: Passive connection from {host} rejected
</pre>

Note that the use of the server host's DNS name, or its IP address, in the
setting up of the ssh tunnel assumes that the routing of traffic to the
host's own IP address will be short-circuited in the kernel and thus not
actually be transmitted on the wire. On modern kernels this is a fair
assumption, but may not always be the case. For the truly paranoid, use
of <code>localhost</code> or <code>127.0.0.1</code> as the remote-addr
parameter in the ssh tunnel command would cause traffic on host to
be sent over its loopback address, and not over the network. However, this
will prevent data transfers from working altogether. The author has a 
patch for scenarios like this; if interested, please contact him directly via
email.

</body>
</html>

${this.title}

Code Editor : SSH.html