1<global>',   
  2  
  3# '<virtualhost>', and '<anonymous>'. These are all explained below.   
  4  
  5#   
  6  
  7# NOTE ABOUT DEFAULT, GLOBAL, ANONYMOUS, AND VIRTUAL BLOCKS:   
  8  
  9#   
 10  
 11# There are four types of 'contexts' in this file; three of them are   
 12  
 13# explicitly marked and one is a catch-all. The three explicit contexts   
 14  
 15# are the <global>...</global> block, the <anonymous>...</anonymous>   
 16  
 17# block, and the <virtualhost>...</virtualhost> block (which isn't   
 18  
 19# included in this sample). Many people just starting with ProFTPD   
 20  
 21# seem to have trouble understanding the way these blocks nest and   
 22  
 23# what they do.   
 24  
 25#   
 26  
 27# You should understand that any directive that *isn't* inside a   
 28  
 29# <virtualhost> block is part of the default server configuration. It   
 30  
 31# doesn't matter if it's at the end of the file, between other   
 32  
 33# <virtualhost> blocks, or at the start of the file -- if it's not   
 34  
 35# contained by a <virtualhost> ... </virtualhost> pair, it's applied to   
 36  
 37# the default server.   
 38  
 39#   
 40  
 41# First of all, <global> blocks set defaults for *every* server listed   
 42  
 43# in the proftpd.conf file, including any <virtualhost> blocks. They do   
 44  
 45# not define an ftp server; it's just a shorthand way of specifying a set   
 46  
 47# of directives in one place instead of in multiple spots.   
 48  
 49#   
 50  
 51# Second, <anonymous> blocks do not define a server. They define a   
 52  
 53# particular service that an FTP server provides. You can have   
 54  
 55# <anonymous> blocks in the default server configuration, or in   
 56  
 57# <virtualhost> blocks, but the <anonymous> blocks are conceptually a   
 58  
 59# *part* of a server, they do not define a server in and of themselves.   
 60  
 61#   
 62  
 63# Third, <virtualhost> blocks define servers which are in addition to   
 64  
 65# the default server, but they are *completely* separate in setup,   
 66  
 67# except that they inherit any directives in a <global> block.   
 68  
 69# <virtualhost> blocks can have their own <anonymous> blocks, and must   
 70  
 71# have their own IP or Port (since the FTP protocol doesn't support   
 72  
 73# true name-based virtual hosts, like HTTP does).   
 74  
 75#   
 76  
 77# Finally, you should realize that all these explicitly-marked blocks   
 78  
 79# are optional. The simplest configuration file will have no   
 80  
 81# <virtualhost> blocks and no <anonymous> blocks. If you don't want   
 82  
 83# anonymous logins, simply remove the anonymous block from this sample   
 84  
 85# configuration file. If you want to configure a virtual host, simply   
 86  
 87# add a complete set of server directives inside a <virtualhost>   
 88  
 89# block.   
 90  
 91  
 92  
 93  
 94  
 95ServerName "ProFTPD Default Installation"   
 96  
 97ServerType standalone   
 98  
 99DefaultServer on   
100  
101  
102  
103# Port 21 is the standard FTP port.   
104  
105Port 21   
106  
107  
108  
109# Umask 022 is a good standard umask to prevent new dirs and files   
110  
111# from being group and world writable.   
112  
113Umask 022   
114  
115  
116  
117# We put our mod_sql directives in a <global> block so they'll be   
118  
119# inherited by the <anonymous> block below, and any other <virtualhost>   
120  
121# blocks we may want to add. For a simple server these don't need to   
122  
123# be in a <global> block but it won't hurt anything.   
124  
125<global>   
126  
127  
128  
129# Specify our connection information. Both mod_sql_mysql and   
130  
131# mod_sql_postgres use the same format, other backends may specify a   
132  
133# different format for the first argument to SQLConnectInfo. By not   
134  
135# specifying a fourth argument, we're defaulting to 'PERSESSION'   
136  
137# connections -- a connection is made to the database at the start of   
138  
139# the session and closed at the end. This should be fine for most   
140  
141# situations.   
142  
143SQLConnectInfo proftpd@localhost:3306 ftp iloveyou   
144  
145  
146  
147# Specify our authentication schemes. Assuming we're using   
148  
149# mod_sql_mysql, here we're saying 'first try to authenticate using   
150  
151# mysql's password scheme, then try to authenticate the user's   
152  
153# password as plaintext'. Note that 'Plaintext' isn't a smart way to   
154  
155# store passwords unless you've got your database well secured.   
156  
157SQLAuthTypes Backend Plaintext   
158  
159  
160  
161# Specify the table and fields for user information. If you've   
162  
163# created the database as it specifies in 'README.mod_sql', you don't   
164  
165# need to have this directive at all UNLESS you've elected not to   
166  
167# create some fields. In this case we're telling mod_sql to look in   
168  
169# table 'users' for the fields 'username','password','uid', and   
170  
171# 'gid'. The 'homedir' and 'shell' fields are specified as 'NULL' --   
172  
173# this will be explained below.   
174  
175SQLUserInfo users userid passwd uid gid homedir shell   
176  
177  
178  
179# Here we tell mod_sql that every user it authenticates should have   
180  
181# the same home directory. A much more common option would be to   
182  
183# specify a homedir in the database and leave this directive out. Note   
184  
185# that this directive is necessary in this case because we specified   
186  
187# the homedir field as 'NULL', above. mod_sql needs to get homedir   
188  
189# information from *somewhere*, otherwise it will not allow access.   
190  
191# SQLDefaultHomedir "/tmp"   
192  
193  
194  
195# This is not a mod_sql specific directive, but it's here because of   
196  
197# the way we specified 'SQLUserInfo', above. By setting this to   
198  
199# 'off', we're telling ProFTPD to allow users to connect even if we   
200  
201# have no (or bad) shell information for them. Since we specified the   
202  
203# shell field as 'NULL', above, we need to tell ProFTPD to allow the   
204  
205# users in even though their shell doesn't exist.   
206  
207RequireValidShell off   
208  
209  
210  
211# Here we tell mod_sql how to get out group information. By leaving   
212  
213# this commented out, we're telling mod_sql to go ahead and use the   
214  
215# defaults for the tablename and all the field names.   
216  
217SQLGroupInfo groups groupname gid members   
218  
219  
220  
221# For small sites, the following directive will speed up queries at   
222  
223# the cost of some memory. Larger sites should read the complete   
224  
225# description of the 'SQLAuthenticate' directive; there are options   
226  
227# here that control the use of potentially expensive database   
228  
229# queries. NOTE: these arguments to 'SQLAuthoritative' limit the way   
230  
231# you can structure your group table. Check the README for more   
232  
233# information.   
234  
235SQLAuthenticate users groups usersetfast groupsetfast   
236  
237  
238  
239# Finally, some example logging directives. If you have an integer   
240  
241# field named 'count' in your users table, these directives will   
242  
243# automatically update the field each time a user logs in and display   
244  
245# their current login count to them.   
246  
247# SQLNamedQuery getcount SELECT "count, userid from users where userid='%u'"   
248  
249# SQLNamedQuery updatecount UPDATE "count=count+1 WHERE userid='%u'" users   
250  
251# SQLShowInfo PASS "230" "You've logged on %{getcount} times, %u"   
252  
253# SQLLog PASS updatecount   
254  
255  
256  
257# close our <global> block.   
258  
259</global>   
260  
261  
262  
263  
264  
265# To prevent DoS attacks, set the maximum number of child processes   
266  
267# to 30. If you need to allow more than 30 concurrent connections   
268  
269# at once, simply increase this value. Note that this ONLY works   
270  
271# in stan</global></global></virtualhost></anonymous></global></virtualhost></anonymous></virtualhost></anonymous></virtualhost></global></virtualhost></anonymous></virtualhost></anonymous></anonymous></virtualhost></global></virtualhost></virtualhost></anonymous></virtualhost></global>