Free ftp server connections software for linux

SYNOPSIS

# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);

# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );

die "oops: ".$c->lastError unless $c->connect();

$c->register_beat(10, &every_10_seconds);

$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);

$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth

$c->send( );

$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.

Pure FTP Server is a fast, production quality, standards-conformant FTP server based on Troll-FTPd. Pure FTP Server has no known vulnerability, it is trivial to set up, and it is especially designed for modern kernels.
Features include PAM support, IPv6, chroot()ed home directories, virtual domains, built-in ls, FXP protocol, anti-warez system, bandwidth throttling, restricted ports for passive downloads, an LDAP backend, XML output, and more.
Beginners can install a Pure-FTPd server in 5 minutes. It can be as simple as installing the package, typing "pure-ftpd &" and... thats all. You already have a running server, and clients can start to connect.
Theres no need to review any long and complex configuration file, where possible mistakes could have security and reliability implications. Pure-FTPd uses simple command-line switches to enable the features you need.
You can limit the number of simultaneous users, limit their bandwidth to avoid starving your ADSL or cable-modem link, hide system files (chroot), have upload/download ratios, and moderate new uploads.
Custom messages can be displayed at login-time (even changing fortune files) and when an user enters a new directory. Also, to avoid your disks being filled up, you can defined a maximal percentage, and new uploads will be disallowed once this percentage is reached.
The FXP (server-to-server) protocol is implemented. It can be available for everyone, or only for authenticated users.
Kiddies are using common brute-forcing tools that are trying to discover hidden directories. Pure-FTPd provides a protection against this. Anonymous access is secure by default. For instance, users cant access dot-files (.bash_history, .rhosts, ...) unless you explicitely enable this.
And to watch whos doing what, the pure-ftpwho command shows a table with currently active sessions, how much bandwidth is taken by every user, what files they are uploading or downloading, where they are coming from, etc.
Enhancements:
- User names can now be up to 127 characters long.
- Compilation with PAM support has been fixed on Mac OS X, and the MySQL PASSWORD() function can now be used with MySQL >= 4.1.
- Logging now has the correct timezone.
- Support for charset conversions (RFC2640) has been implemented. Large files are now handled by default, using sendfile64() if possible. SITE UTIME and OPTS MLST have been implemented.
- MySQL queries can now include multiple statements and call MySQL 5 stored procedures.
- Transferring a lot of small files is now much faster than in previous versions.

Net::FTPServer is a secure, extensible and configurable Perl FTP server.
SYNOPSIS
ftpd [--help] [-d] [-v] [-p port] [-s] [-S] [-V] [-C conf_file]
[-P pidfile] [-o option=value]
Net::FTPServer is a secure, extensible and configurable FTP server written in Perl.
Current features:
- Authenticated FTP access.
- Anonymous FTP access.
- Complete implementation of current RFCs.
- ASCII or binary type file transfers.
- Active or passive mode file transfers.
- Run standalone or from inetd(8).
- Security features: chroot, resource limits, tainting, protection against buffer overflows.
- IP-based and/or IP-less virtual hosts.
- Complete access control system.
- Anonymous read-only FTP personality.
- Virtual filesystem allows files to be served from a database.
- Directory aliases and CDPATH support.
- Extensible command set.
- Generate archives on the fly.
Installation:
A standard ftpd.conf file is supplied with the distribution. Full documentation for all the possible options which you may use in this file is contained in this manual page. See the section CONFIGURATION below.
After doing make install, the standard ftpd.conf file should have been installed in /etc/ftpd.conf. You will probably need to edit this file to suit your local configuration.
Also after doing make install, several start-up scripts will have been installed in /usr/sbin/*ftpd.pl. (On Debian in /usr/bin or /usr/local/bin). Each start-up script starts the server in a different configuration: either as a full FTP server, or as an anonymous-only read-only FTP server, etc.
The commonly used scripts are:
- /usr/sbin/ftpd.pl
- /usr/sbin/ro-ftpd.pl
The first script is for the full FTP server.
These scripts assume that the perl interpreter can be found on the current $PATH. In the rare situation when this is not the case, you may need to edit these scripts.

Net::Server is an extensible, general Perl server engine.
SYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).

BitWise Routing Server allows multiple PCs behind a router to make direct connections.

The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.

As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.

The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).

The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.

The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.

Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.

In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.

If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.

Setting up the physical router

The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.

The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).

Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.

Configuring BitWise to use the Routing Server

In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).

Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.

Registration with the Routing Server

Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.

It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.

Using the Routing Server

Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.

The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.

ftpcluster provides a system which integrates several FTP servers into one.
ftpcluster integrates a number of individual FTP servers into a single large server. You can think of it as a network disk array with FTP as the access protocol.
Main features:
- FTP protocol
ftpcluster speaks enough FTP to upload, download, delete and rename files. You can also create, delete and rename directories.
- The cluster is working
Files can be distributed over your cluster nodes. ftpcluster knows how to handle files on your nodes.
- Replication
Files can be replicated to two or more node for fail-over situations.
- User authentication
Version 1.0.3: Users must authenticate against a local password file. Password are actually stored in cleartext.
- Filenames
Version 1.0.3: Filenames are not limited to a certain set of characters. Theres optional support for blanks and/or arbitrary characters in filenames. You can however restrict your users to usual UNIX filename conventions.
- Partial support for FTP REST command
Version 1.0.7: The cluster supports the REST command for downloads, for uploads only if the file is stored on the cluster.
- System checker
Since version 1.0.9 there are programs to check and repair cluster nodes.
Enhancements:
- Programs to check and repair the cluster were added.
- The FXP configuration documentation was started.

FTP SyncAgent is a software that keeps a local folder and a remote FTP folder in sync. All what you need to do is to create a Java properties file (explained here) and start it.

Currently there is only a console-based UI and you will be asked for files to download/upload or remove.

Later on, I will provide a more intelligent agent module which can be pre-configured for common descision patterns and which will be able to choose automatically what to do. Thus, the agent should be able to run as a cron job and periodically check for required updates.

Quick Start

1. Download the latest release of FTP SyncAgent and the two dependent libraries: Jakarta Commons Net and ORO (you will only need the two JAR files commons-net-[version].jar and jakarta-oro-[version].jar).
2. Create a properties (config) file for each directory to sync, e.g. syncedFolder.properties and save it somewhere, lets say in /home/myUser/syncedFolder.properties. The file should contain at least the following lines (you can copy it from here!):

host=ftp.theFTPserver.com
port=21
user=myUserName
pass=myPassword
remoteFolder=absolutePathToTheLocalFolderToSync
localFolder=relativePathToTheRemoteFolderToSync
verbose=true
passive=true
ignore=.backup .bak ~

The host, port, user, and pass properties should be clear, the remoteFolder is the path to the remote folder relative to the FTP home directory (e.g. /mySyncedFiles), the localFolder is the absolute directory path to the local folder to be synced (e.g. /home/myUser/aFolderToSync). The property verbose is just for a more detailed output to the shell when sychronising, passive will enable (or disable) a passive connection to the server (if you are behind a firewall our gateway router), and using ignore you can specify file suffices to exclude.
3. Setup the classpath or specify it when starting (as shown here at the next step). The classpath must contain the two dependent JARs as described under requirements and the FTP SyncAgent JAR file ftpsyncagent.jar.
4. Now you can run FTP SyncAgent with the following command (you must adjust the path to the JAR files according to your directory structure! Create a shell script or batch file for an easier startup):

java -cp /opt/javalibs/ftpsyncagent.jar:/opt/javalibs/commons-net-1.4.1.jar:
/opt/javalibs/jakarta-oro-2.0.8.jar at.langegger.ftpsa.SyncAgent
/home/myUser/syncedFolder.properties

The basic usage is:

java -cp [jar-files] at.langegger.ftpsa.SyncAgent [custom properties-file]

5. Thats all. For any questions, contact me (via e-mail, address below).

ftpsync provides a tool for synchronizing directories over FTP.

ftpsync is a tool that allows updates to be incrementally and recursively made to remote FTP servers. It examines time stamps and sizes, and is designed to operate in a manner similar to rsync.

ftpsync implements the missing recursive PUT FTP command.