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 : Redis.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD: Redis</title>
</head>

<hr>
<center><h2>ProFTPD: Redis</h2></center>
<hr>

What is Redis? 
<a href="https://redis.io/">Redis</a> is an open-source, high performance
memory object caching system. A simple (and effective) key/value store
accessible, efficiently, over the network.

How Can Redis Be Useful for ProFTPD? 
Like any high-performance object store, Redis offers several possibilities to a
server like ProFTPD. Many sites use Redis for caching; it can also be
used as an efficient shared storage mechanism, for sharing data among many
different servers. And for ProFTPD specifically, the shared storage aspect is
what is most useful. Things like SSL/TLS sessions can be cached and shared
across a cluster of <code>proftpd</code> servers, as can ban lists for
badly-behaved clients.

Enabling Redis Support for ProFTPD 
OK, so you are interested enough in the possibilities that Redis offers that
you want to try it out. Excellent! To do this, you will first need to make
sure to build your <code>proftpd</code> executable using the
<code>--enable-redis</code> configure option. The <code>--enable-redis</code>
configure option automatically adds the
<code><a href="../modules/mod_redis.html">mod_redis</a></code> module to
your <code>proftpd</code> build.

The <code>mod_redis</code> module uses the <code><a href="https://github.com/redis/hiredis">hiredis</a></code> library for talking to Redis servers. If your
<code>hiredis</code> library is installed in a non-standard location, you may
need to tell the ProFTPD build system where to find the <code>hiredis</code>
header files and libraries using the <code>--with-includes</code> and
<code>--with-libraries</code> configure options.

There are other modules which make use of Redis support when available, such as
<code><a href="../contrib/mod_tls_redis.html">mod_tls_redis</a></code>.
Thus to take advantage of modules like this, putting everything together, your
configure command might look like this:
<pre>
 $ ./configure --enable-redis \
 --with-modules=...:mod_tls_redis:... \
 --with-includes=/path/to/hiredis/include \
 --with-libraries=/path/to/hiredis/lib
</pre>

Configuring <code>mod_redis</code> 
Now that you have compiled <code>proftpd</code> with the <code>mod_redis</code>
module, you need to add the necessary <code>mod_redis</code> directives to
your <code>proftpd.conf</code>. The following example demonstrates this:
<pre>
 &lt;IfModule mod_redis.c&gt;
 # Enable mod_redis
 RedisEngine on

# Tell mod_redis where to log its messages
    RedisLog /path/to/proftpd/redis.log

# Tell mod_redis where to find the Redis server
 RedisServer 192.168.0.10:6379
 &lt;/IfModule&gt;
</pre>
If you wish to see more detailed logging, at least while you are setting up
your Redis servers for ProFTPD, you can enable trace logging for the
<code>redis</code> trace channel using e.g.:
<pre>
 TraceLog /path/to/proftpd/trace.log
 Trace DEFAULT:10 redis:20
</pre>

Using Redis for Shared Storage 
You have now compiled support for Redis into ProFTPD, and you have told the
<code>mod_redis</code> module where to find your Redis servers. Is that all
you need to do? No. Now you need to tell <code>proftpd</code> modules which
bits of data to store in your Redis server.

Currently, only two modules can take advantage of Redis support:
<code><a href="../contrib/mod_ban.html">mod_ban</a></code> and
<code><a href="../contrib/mod_tls_redis.html">mod_tls_redis</a></code>.

First, let us examine <code>mod_ban</code> and how it would use Redis. The
<code>mod_ban</code> module manages ban lists, lists of clients/users which
have been banned for various reasons. These lists are stored in shared memory
by default; this works for a single <code>proftpd</code> server, but if a badly
behaved client is banned by one <code>proftpd</code> server in pool of servers,
that client can then connect to a different server which might not have a ban
for that client -- and the client then gets another chance to be naughty. To
configure <code>mod_ban</code> so that it stores its ban lists in Redis,
simply use the following in your <code>proftpd.conf</code>:
<pre>
 &lt;IfModule mod_ban.c&gt;
 BanEngine on

# ...other mod_ban directives...

# Tell mod_ban to store its ban lists using Redis
 BanCache redis
 &lt;/IfModule&gt;
</pre>
With this, <code>mod_ban</code> will use Redis (as well as shared memory) for
reading/writing its ban lists. And this, in turn, means that other
<code>proftpd</code> servers' <code>mod_ban</code> modules can see those bans,
and reject the badly behaved clients across the pool/cluster.

The <code>mod_tls_redis</code> module uses Redis servers for storing SSL/TLS
sessions; SSL/TLS session caching can greatly improve SSL/TLS session handshake
times, particularly for data transfers using SSL/TLS. If you have a pool of
<code>proftpd</code> servers, and you have FTPS clients which may connect to a
different node every time, caching the SSL/TLS session data in a shared storage
mechanism like Redis can be quite beneficial.

To use Redis for SSL/TLS session caching, then, you use the <a href="../contrib/mod_tls.html#TLSSessionCache"><code>TLSSessionCache</code></a> directive of the <code>mod_tls</code> module, using something like this
in your <code>proftpd.conf</code>:
<pre>
 &lt;IfModule mod_tls.c&gt;
 TLSEngine on

# ...other mod_tls directives...

&lt;IfModule mod_tls_redis.c&gt;
 # Tell mod_tls to cache sessions using Redis
 TLSSessionCache redis:
 &lt;/IfModule&gt;
 &lt;/IfModule&gt;
</pre>
That's it. The <code>mod_tls</code> module now knows to give the SSL/TLS
session data to <code>mod_tls_redis</code>, and <code>mod_tls_redis</code>
knows how to talk to the Redis server using <code>mod_redis</code>.

<a name="FAQ">
Frequently Asked Questions 
Question: If I don't use Redis, are there other
ways for sharing data (such as ban lists) among different <code>proftpd</code>
instances? 
Answer: It might be possible using <code>mod_sql</code>
and some <code>SQLLogInfo</code> directives, but that would only work for very
specific information. For sharing things like ban lists and SSL/TLS sessions
across a cluster of <code>proftpd</code> servers, Redis (or
<a href="Memcache.html">Memcache</a>) support is recommended.

Question: Can I use <code>mod_redis</code> to cache
frequently accessed files, similar to <code><a href="http://wiki.nginx.org/HttpMemcachedModule">nginx+memcache</a></code>? 
Answer: No. And in reality, caching of files like that
will probably not give you the same performance gain for FTP transfers as it
can for HTTP transfers.

Why not? Many HTTP transfers are for dynamically generated pages; the cost of
generating each page is expensive, and the generated content may not change
that frequently (relative to the rate of requests). FTP transfers, by contrast,
are for static files; FTP servers do not (usually) dynamically generate
the bytes of the files being downloaded. The cost of reading files from disk
is probably less than reading files from Redis, over the network, even
a LAN.

Now the above may not be true in all cases -- there may be FTP servers
serving files from network-mounted filesystems (e.g. NFS, CIFS
et al). And for these very specific cases, having a cache of frequently
access files on closer storage such as local disk (or Redis) could make a big
difference; please contact the ProFTPD Project if you find yourself in this
situation, and we will see what can be done to help.

Question: Why do I see the following error when
<code>proftpd</code> starts up? 
<pre>
 mod_tls_redis/0.1: notice: unable to register 'redis' SSL session cache: Redis support not enabled
</pre>
Answer: This message means that your
<code>proftpd</code> server has <code>mod_tls_redis</code> built and
loaded, but your <code>proftpd</code> server was not built
with Redis support (i.e. the <code>--enable-redis</code> configure
option was not used when compiling <code>proftpd</code>).

The above is not a fatal or worrisome error; it is merely pointing out that
some of your modules want to use a feature that was not enabled.

</body>
</html>

${this.title}

Code Editor : Redis.html