@DATABASE ftp4all.guide @NODE Main "FTP4ALL - FTP Server" @{B} FTP4ALL (Amiga Version) Version 2.25b @{UB} Amiga Version by @{B}FireBall Interactive@{UB} http://www.fireball.csti.ru @{" Introduction " link INTRODUCTION} @{" Requirements " link REQUIREMENTS} @{" Install " link INSTALL} @{" Configurations " link CONFIGURATION} @{" Users & Groups " link USER&GROUP} @{" History " link HISTORY} @{" Copyright " link COPYRIGHT} @{" Authors " link AUTHORS} @ENDNODE @NODE INTRODUCTION "FTP4ALL - Introduction" @{B}What is FTP4ALL ?@{UB} FTP4ALL is a FTP server program for UNIX systems. Unlike existing FTP servers, e.g. WUFTPD, FTP4ALL does not require an root account to install it. Every user that can compile source code can install it, thereby providing a facility to share files with friends. All that you need is a C compiler, and I dont know a UNIX system that does not have one. @{B}Features.@{UB} o Free source code available, compiles on most UNIX platforms o Server runs under normal user accounts (no superuser privileges needed) o Permissions can be given to files and directories, similar to UNIX o User classes: anonymous / registered / superuser o IP range for login for every user o Private mode o Number of simultaneous logins can be set for each user o Counts upload and downloaded amount for every user o Download credit system o Download counter for every file and directory o Logs user activities, also through external program o Customizable FTP replies, with variables o Online server administration (view/add/edit/remove users/groups) o Passive FTP o Archive checking through external program/script o Top ten lists with variables o Duplicate file checking o User scripts, new commands with external scripts/programs o Intelligent ChDir o Filename / directory name conversion o Readme files o DES encrypted user file o User information field @{B}Files and Directories.@{UB} FTP4ALL uses a file protection scheme similar to that of UNIX. Permissions can be given to three instances: owner, group and world (others). Rights can be assigned to directories and files. For files, the rights are almost the same, with the exception that there is no execute right (but this is not needed for an ftp server). For directories, the rights differ from the UNIX rights. There are not three rights, but seven. These seven rights, that can be given to each of the three instances are: · access The right to change the permissions of this directory and the files within, and to remove the directory. · chdir The permission to change to this directory. · list The permission to list the contents of the directory. · mkdir The right to create a subdirectory in this directory. · put The permission to upload a new file to this directory. · no limit This is not really a right. When you set this flag, then uploads and downloads to/from this directory do not increase the user's upload/download amount. · get If this is set, created files get read permission. · overwrite If this is set, created files get write permission. For files, the permissions are mostly like in UNIX: · read The permission to read the file - heird from the get right. · write The right to overwrite, delete or rename the file - heird from the overwrite right. · chmod The right to change the file permissions - heird from the access right. Access permissions for a directory and the files within are stored in a special file in the same directory, .permissions by default. This file simply contains user id and group id of the owner and the permissions for owner, group and others - for the directory itself and for each file in the directory. If a readme file exists in a directory, its contents is displayed whenever a user changes to this directory. @{B}Users.@{UB} There are four classes of users: · anonymous This user may log in anonymously, i.e. with his e-mail address as password. Login is possible from any IP address. There is a maximum number of anonymous users that can be logged in simultaneously. In addition, anonymous access can be fully disabled by setting this number to zero. · normal/registered This user has an account with the server, and may log in with his user name and password. There is a maximum number of registered users that can be logged in at the same time. An IP range can be set individually for each user, allowing him to log in from certain IP adresses only. · superuser This user also needs login and password, but has unlimited access to files and directories of the server, i.e. access permissions do not count. Furthermore, he can use all SITE commands, allowing him to modify users, groups and other server parameters. The maximum number of users does not apply for superusers. However, IP check applies, superusers can only log in from the given IP range (like registered users), thereby improving security. · template This is not an ordinary user account like the other three ones. It is created in order to create other user accounts faster. When creating a normal user account, a template can be specified. Then all user data from the template are copied to the new user account. Users are defined in a user file. @{B}Groups.@{UB} Like in UNIX, users are moved together in groups. Every user must be in one group. This group is called the primary group. Furthermore, a user can be in up to eight secondary groups. There are two differences between the primary group and the secondary groups. The first is, that all files and directories that the user creates get only the primary group id. Second, the user can only run scripts from his primary group. Groups can be set up in a special group file. @{B}Files and Configuration.@{UB} The server itself consists of two binaries, named ftpd and ftps. ftpd is the daemon. Its purpose is to set up the FTP server and to wait for connections. It only terminates by request (shutdown or signal). Every time a client connects, ftpd spawns ftps. ftps then handles the session with the client. ftpd reads a configuration file on startup, named ftpd.conf by default. This file contains the basic configuration, e.g. the port number of the server and the name of the base directory, messages to display and so on. Two more configuration files are also very important: The user and group files. They are named .users and .groups by default and contain user and group definitions. They are saved regulary by ftpd, to reflect changes. ftpd also creates two log files by default: ftpd.err and ftpd.log. All errors go in ftpd.err (are there any ??? ;-)). Whenever the server terminates, date, time and reason are also logged in ftpd.err. Session log goes in ftpd.log, i.e. when did a client connect and from where, uploads, downloads and so on. You can define which actions to log in ftpd.conf. @ENDNODE @NODE REQUIREMENTS "FTP4ALL - Requirements" @{B}Amiga FTP4ALL require:@{UB} 1) An Amiga :) 2) TCP/IP Stack (AmiTCP/AmiTCP-GENESiS/Miami/MiamiDeluxe/Inet225) 3) Ixemul/Ixnet.library 4) Internet connections or local network. @ENDNODE @NODE COPYRIGHT "FTP4ALL - Copyright" @{B} FTP4ALL is FREE software, and distributed under GNU GENERAL PUBLIC LICENSE. GNU GENERAL PUBLIC LICENSE@{UB} Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @{B} Preamble@{UB} The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. @{B} GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @{UB} 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. @{B} NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS @{UB} @ENDNODE @NODE INSTALL "FTP4ALL - Installation" @{B}Server guide:@{UB} ftpd - reads the configuration file and accepts connections from clients. also spawn ftps. ftps - handles communication with the client. @{B}Installing:@{UB} 1) Make dir @{B}ftp4all@{UB} in your AmiTCP:serv/ or where you want. 2) Copy @{B}ftpd, ftps, ftpd.conf, users, groups@{UB} to AmiTCP:serv/ftp4all or where you make your dir. 3) Change @{B}ftpd.conf, users, groups@{UB} what you need. Warning! Path like @{B}Intenet:Miami/@{UB} not accepted, use only @{B}/internet/miami/@{UB}. @{B}Running:@{UB} Warning! Running only in standalone mode. @{B}cd amitcp:serv/ftp4all@{UB} (or cd ) @{B}stack 200000@{UB} (not obligatory, but recommended) @{B}run >NIL: ftpd@{UB} (for test you can yourself check it by: @{B}telnet 127.0.0.1 21)@{UB} @{B}Stopping:@{UB} 1) break (where - number the ftpd task) 2) @{B}quote SITE SHUTDOWN@{UB} (only by superuser) @ENDNODE @NODE CONFIGURATION "FTP4ALL - Configuration" FTPD needs a configuration file to set up the service. All configuration options are described below. In the configuration file, all empty lines are ignored, as well as all lines starting with a "#" character. The configuration file must be in the current directory. If it is not in the current directory, run ftpd with the full name of the configuration file as first parameter (e.g. ftpd ftpd.conf). @{B}alternativeserverprogram@{UB} Syntax : alternativeserverprogram Example: alternativeserverprogram /usr/sbin/wu.ftpd Default: disabled This is to run two services on one port (Service Splitter). Must turn option private on. When a non-authorised connection is encountered, the alternative service is started. (Versions lower than 2.09 would close this connection immediately) Give alternative service program in configuration file with option: AlternativeServerProgram Alternative service is invoked in inetd mode. This means any serive that is run by inetd can be used. Therefore, it is not possible to run two ftp4all services ! Services that require root privileges require that you run ftp4all as root. Or use the following trick: Example: Alternative service is wu-ftpd / You need superuser privileges to run wu-ftpd !!! 1. Compile & install ftp4all as non-privileged user 2. Include configuration option for alternative service in ftpd.conf (AlternativeServerProgram /usr/sbin/wu.ftpd) 3. Activate set-user-bit on ftp4all ( chmod u+s ftpd ) 4. become root (superuser) 5. run ftpd Note: ftpd will run in non-privileged mode and will only temporary aquire superuser rights for the following two tasks: 1. to bind the service to a socket (ports <1024 are possible!) 2. to execute the alternative service wu-ftpd ftps runs completely as non-privileged user. All files are stored with non-privileged user as owner (as usual). @{B}basedir@{UB} Syntax : basedir Example: basedir /home/ftp/root Default: /home/ftp This specifies the base directory. The base directory appears as root directory when someone logges into the server. @{B}bouncer@{UB} Syntax : bouncer Example: bouncer 192.168.1.1 Default: (none) With this option you can use your server with a so-called "bouncer". F4A is full working with the rftpd-bouncer. You can get it on the rFtpd-Homepage. @{B}cdpath@{UB} Syntax : cdpath Example: cdpath /cdrom 0 1 0x7F1300 Default: (none) With this option you can assign access permissions to directories that are on read-only filesystems (mostly cd roms). The specified directory and all following subdirectories get the specified access permission. specifies the user id of the owner, the group of the owner and the access permissions. permissions is an integer and is best specified in hexadecimal form (as shown in the example). There, the first byte gives the rights of the owner, the second the right of the group and the third the rights of other users. The next table shows which bits mean which right. Add the values to form the right: 0x01 - chdir 0x02 - list 0x04 - mkdir 0x08 - chmod 0x10 - get 0x20 - put 0x40 - overwrite 0x80 - no limit You can have as many cdpath statements in the configuration file as you want. The paths are checked by the server in the order in which they appear in the configuration file. In the above example, if you do not want that group members can access /cdrom/private but all other parts of /cdrom should be accessible, then add the line cdpath /cdrom/private 0 1 0x7F0000 before cdpath /cdrom 0 1 0x7F1300. This will cause the server to check /cdrom/private first, and as it has no access permissions, access to this directory will be refused. If you change the order, /cdrom is examined first and because /cdrom/private is a subdirectory of /cdrom, it has the same permissions and access is granted. @{B}cdupmsg@{UB} Syntax : cdupmsg cdupmsg Syntax : cdupmsgfile Example: cdupmsg CDUP command successful. Directory changed to: %s cdupmsg Example: cdupmsgfile /home/ftp/msgs/cdup.msg Default: CDUP command successful. This is the first option of many that can be used to customize FTP replies. This message is sent when a successful CDUP command was performed. The message itself can go over multiple lines and can contain variables. Variables begin with a % and are replaced by their values when the message is sent. You can either write the message in the configuration file or to a message file. In the first case, the message must be included between the name of the message, as shown in the example. In the latter case, the file that contains the message must be specified. The syntax is the name of the message followed by file and then the filename (with full path) as shown above. The advantage of this method is, that the messages can be easily changed while the server is running. Whenever the server detects that the message file has been modified, it reads it again. @{B}chdirmsg@{UB} Syntax : chdirmsg chdirmsg Syntax : chdirmsgfile Default: CWD command successful. This is the message that is sent when the user changes the directory with the CD command. For more details see cdupmsg. @{B}check@{UB} Syntax : check [] Example: check .zip unzip -t Default: (none) With this option, the server checks uploaded archives to see if they are ok. This is done by external programs. You have to give the extension of the file and the program that can check files with this extension. parameter gives the parameter that makes the program check the archive. If an archive is corrupt, the upload amount of the uploader does not increase. @{B}checkdupe@{UB} Syntax : check [] Example: checkdupe .zip /home/ftpd/scripts/dupecheck/dupechk Default: (none) This is the interface for an external dupechecker. The syntax is the same as in the check-configuration option. Depending on the exitcode of the external dupecheck program the daemon denies or allows the upload. @{B}checktimeout@{UB} Syntax : checktimeout Example: checktimeout 10 Default: 0 (disabled) This sets a maximum time, which the uploadchecker can use before timeout and gives a error-message to the log and the user that the checker failed. The files remain on the server but the siteop have to check them manually. @{B}delemsg@{UB} Syntax : delemsg delemsg Example: delemsg Please force the siteop to update the dupelist. DELE command successful. delemsg Default: DELE command successful. For example you can specify a script here which updates a dupelist. @{B}dirshortcut@{UB} Syntax : dirshortcut Example: dirshortcut td /Incoming/today With this Option, you can configure shortcuts to often used directories. No matter in wich directory on your server the user is, with a cd he can comfortable jump to often used locations. @{B}downloadmsg@{UB} Syntax : downloadmsg downloadmsg Syntax : downloadmsgfile Default: Transfer completed. This is the message that is sent after a successful file download. For more details see cdupmsg. @{B}dupecheck@{UB} Syntax : dupecheck Example: dupecheck *.zip Default: (none) This option prevents files from being uploaded twice. Files matching the wildcard cannot be uploaded when a file with the same filename exists somewhere on the server. You can specify more than one wildcard by entering this option several times with different wildcards. @{B}dupepath@{UB} Syntax : dupepath Example: dupepath /upload Default: / This options specifies a path from that the dupe checking should be performed. Dupe checking is only performed for uploads in directories below the specified one. Only one directory can be given. @{B}errlogfile@{UB} Syntax : errlogfile Example: errlogfile /home/ftp/ftpd.err Default: ftpd.err ftpd stores runtime error information in this file. Specify a full filename, because otherwise the file is created in the current directory. The default value is therefore not useful. @{B}filenameconversion@{UB} Syntax : filenameconversion Example: filenameconversion 0x11 Default: 0 This option sets a filename conversion function, that is called every time a file is uploaded or directory is created. If one of the events occurr, the name of the file or directory is converted in a special way. The number gives says how the name should be converted. Add values for files and directories: 0x00 - no conversion 0x01 - convert file name to lowercase 0x02 - convert file name to uppercase 0x03 - convert first letter of filename to uppercase 0x04 - convert all spaces of filename into underscores _ 0x10 - convert directory name to lowercase 0x20 - convert directory name to uppercase 0x30 - first letter of directory name to uppercase 0x40 - convert all spaces of directory name to underscores _ @{B}goodbyemsg@{UB} Syntax : goodbyemsg goodbyemsg Example: goodbyemsg Goodbye, %s ! You downloaded %d in this session (%D total). You uploaded %p in this session (%P total). Your upload/download ratio is %r (%R total). See you later ... goodbyemsg Default: Goodbye ! This message is shown when a user logges out. There can be special characters in the message. They will be expanded when the message is shown. @{B}group@{UB} Syntax : group : Example: group root:0 Default: (no default value) This is used to define a user group. gives the name of the group. The maximum name length is 10 characters. However, in directory listings, only the first eight characters are show, so try to set up group names that have a maximum length of eight characters. is a numeric value that gives an unique group identifiaction number. Creating a group with this option is not advised. Use the groupfile command instead. @{B}groupop@{UB} Syntax : groupop Example: groupop group/list kick user/passwd Default: (no default value) This configuration option sets the rights a user with the groupop status should have. A user with the groupop status can apply all the rights you've set with this option to all users in his group. The rights can be one of the following: operator/edituser rights ---------------------------------------------------------- enable - enable user account disable - disable user account group/all - all group rights (following) group/add - add group group/change - change group group/remove - remove group group/list - list all groups groups - list/change groups of a user kick - kick user max - limit maximal user count user/all - all user rights (following) user/add - add users to the group user/passwd - set user (new) password user/change/all - all user change rights (following) user/change/ip - change user ip(s) user/change/stats - change user statistics user/change/ratio - change user ratio user/change/other - change other user rights (rest) user/list - list all users user/remove - remove users from site user/reset - reset user account transfer statistics @{B}groupfile@{UB} Syntax : groupfile Example: groupfile /home/ftp/groups Default: .groups File to read more user groups from. Specify a full filename, because the file is saved by the server at certain occasions. @{B}ident@{UB} Syntax : ident [on|off] Example: ident on Default: off This option enables the built in ident-support. If it is enabeled, the server sends on an connection attempt an ident request to the clients host. The response of this request is logged into the logfile, also connections get refused if the server is in private mode and there is no user with a suitable ident@ip added in the userbase. @{B}listmsg@{UB} Syntax : listmsg listmsg Syntax : listmsgfile Default: Directory listing completed. This is the message that is sent after a successful directory listing. For more details see cdupmsg. @{B}log@{UB} Syntax : log {[!]}* Example: log login logout get put Example: log all !list !cd Default: none Log certain user activities. An exclamation mark (!) before the action means that this action is not logged. Not all actions can be logged. By now, only actions regarding Login/Logout and Files/Directories can be logged: all - log everything cd - log change of current directory chmod - log chmod commands del - log removal of files get - log file downloads login - log user logins and login retries logout - log user logout ls - log directory listings md - log make directory commands put - log uploads rd - log removal of directories ren - log rename of files @{B}logfile@{UB} Syntax : logfile Example: logfile /home/ftp/ftpd.log Default: ftpd.log File to log user activities. @{B}logprogram@{UB} Syntax : logprogram [] Example: logprogram /home/ftp/server/logger /home/ftp/server/ftpd.log Default: (none) This specifies a program that should perform the task of a log server. The program is started by FTP4ALL when the server starts. It receives all log messages that go into the log file. The log program must read the messages over stdin and terminate when stdin is closed. It can then perform own functions, e.g. create statistics out of the log information. @{B}loginkick@{UB} Syntax : loginkick Example: loginkick 9 With this option you can enable the "ghost"-kick function for all users. If enabled it allows the user to wipe all their currently logged in clients with logging in as !username (and correct password of course). The kill signal is the signal which is send to the child processes, 9 is secure. @{B}loginretries@{UB} Syntax : loginretries Example: loginretries 3 Default: 10 Specifies the maximum number of login retries. If the number is reached, the control connection to the client is closed. @{B}maxanon@{UB} Syntax : maxanon Example: maxanon 5 Default: 10 Maximum number of anonymous users logged in at the same time. @{B}maxanondomain@{UB} Syntax : maxanondomain Example: maxanondomain 2 Default: 10 Maximum number of anonymous users logged in at the same time from the same domain. maxanonip and maxanondomain are there for preventing an anonymous user from logging in multiple times - and thereby occupying the server. A domain is aaa.bbb.ccc from an IP address aaa.bbb.ccc.ddd. This is not exactly an internet domain, but it does what it is supposed to. @{B}maxanonip@{UB} Syntax : maxanonip Example: maxanonip 1 Default: 10 Maximum number of simultaneous, anonymous logins from an IP. @{B}maxuser@{UB} Syntax : maxuser Example: maxuser 5 Default: 10 Maximum number of registered users logged in at the same time. @{B}mkdirmsg@{UB} Syntax : mkdirmsg mkdirmsg Syntax : mkdirmsgfile Default: MKDIR command successful. This is the message that is sent when the user creates a new directory. For more details see cdupmsg. @{B}other_ip@{UB} Syntax : other_ip Example: other_ip 123.123.123.123 Default: none The other_ip option will tell the ftp-daemon to which IP it should bind in case the host has multiple IP's. @{B}permissionfile@{UB} Syntax : permissionfile Example: permissionfile perm.$$$ Default: .permissions File to store access permissions in. Must be a plain filename (without path), because it is created in every directory. @{B}pidfile@{UB} Syntax : pidfile lt;filename> Example: pidfile /home/ftpd/bin/ftp4all.pid Default: /var/run/ftpd.pid The processid (pid) of the serverprocess gets saved in there on daemon start @{B}port@{UB} Syntax : port Example: port 2048 Default: 21 port to accept connections from. @{B}pre_download@{UB} Syntax : pre_download