• Bug with big files put in a new HPSS directory
• several bug fixes on AIX 5.2 (by Gilles GALLOT)
• Server side: if both -f and -e are used, the listening control port is chosen in the range. moreover an additional option is now available in the configuration file: [no]fixeddataport

Installing the client

Configuring the client

In the bbftpc directory, run:
% ./configure

The configure script accepts the following standard options:

The configure script accepts the following additional options:

The following options should be used in certificate mode only:

Building the client

In the bbftpc directory, run:
% make

Installing the client

In the bbftpc directory, run:
% make install

Binary Windows installation

Configuring the server

In the bbftpd directory, run:
% ./configure

The configure script accepts the following standard options:

The configure script accepts the following additional options:

The following options should be used in certificate mode only:

Building the server

In the bbftpd directory, run:
% make

Installing the server

In the bbftpd directory, run:
% make install

Configuration

It is possible to make the daemon start with options defined in a configuration file. This file is /etc/bbftpd.conf. The syntax is the same of the configuration file for client users (.bbftprc). Available options are described in the BBFTPD man page

Post installation

If you have chosen to run the server through inetd

• Add the line
  bbftp    CONTROLPORT/tcp
  in your /etc/services file where CONTROLPORT is the number you have set in the includes/config.h (usually 5021)
• Add the line
  bbftp stream tcp nowait root ${bindir}/bbftpd bbftpd
  in the /etc/inetd.conf

If your system authentication is PAM

• If you have a /etc/pam.conf file
  • Verify the lines begining by other auth and other account allow login. If it is not the case add special lines for bbftp. The lines to be added will look like:
    bbftp auth required /lib/security/pam_pwdb.so shadow nullok
bbftp account required /lib/security/pam_pwdb.so

• If you have a /etc/pam.d directory
  • Verify the file other and allow login. If it is not the case create a new file called bbftp which will contain two lines looking like:
    auth required /lib/security/pam_pwdb.so shadow nullok
account required /lib/security/pam_pwdb.so

The name of the PAM library may change.

If you have chosen to run the server as a daemon

• Modify the script ${prefix}/etc/bbftpd to add the options you need and to change the values of the GSI variables if you did not use the --with-x509 options during the configuration process.
• To start the daemon run:
  ${prefix}/etc/bbftpd start
• To stop the daemon, run:
  ${prefix}/etc/bbftpd stop
• To restart the daemon (stop and start), run:
  ${prefix}/etc/bbftpd restart
• To see the daemon's status, run:
  ${prefix}/etc/bbftpd status

Ports used by BBFTP

Control connection

Data connection

• Passive mode (client 3 against server 3 only)
  The server listens on ephemeral ports which are sent to the client. These ports can be chosen in a range defined at compile-time or at run-time.
• Non-passive mode (other configurations)
  The server initiates the data connection(s) after the client has sent him its private IP address and the listening port(s). This(these) port(s) is(are) ephemeral ports (>1023). (it is possible to define a range of ports when starting the client using the -D option) The server can then establish the connection(s) to the specified port(s) from its port std-1 (ie 5020 by default).

Working with Transfer URLs (TURL)

BBFTP support 3 types of TURL:

Working with external software

Zlib

External software required (on both client and server hosts)

• GSI (Grid Security Infrastructure) from the Globus 2 Toolkit (2.0 or 2.2)

Collecting transfer data

Building statistics

Implementing a private authentication module

On the client side

Write your authentication code in the file bbftp/bbftp_private_user.c.

• extern char *username;

  This variable contains the username given on the command line (-u option).

• extern char *privatestr;

  This variable contains the string given on the command line with the -P option (or NULL if not used).

• int bbftp_private_getargs(char *logmessage)

  This routine is called at the begining of the login sequence (just before setting the process in background if needed) in order to allow the programmer to set variables or to request input from the user.

  The return code and the variables are explained in the file.

  After having called this routine the main program will exchange RSA keys with the server in order to crypt all messages sent during the authentication procedure. Then the hand will be given to the next routine :

• int bbftp_private_auth(char *logmessage)

  This routine will allow the user exchange data between the client and the server. For that it will use two routines bbftp_private_recv and bbftp_private_send whose descriptions are given in the bbftp_private_user.c file.

  When all this data exchange has ended, the routine will return to main code with a return code of 0 in case of success or with a return code of -1 and the string logmessage filled in case of error.

On the server side

Write your authentication code in the file bbftpd/bbftpd_private_user.c.

• extern char currentusername[MAXLEN];

  It has to be filled by the bbftpd_private_auth routine.

• int bbftpd_private_auth(char *logmessage)

  As on the client side, this routine will exchange data using bbftpd_private_send and bbftpd_private_recv routines (whose decriptions are given in the bbftpd_private_user.c file), do all checks needed and return 0 in case of success or -1 and the string logmessage filled in case of error.

Building BBFTP with a private authentication module

On the client side

In the bbftpc directory, run
% ./configure --enable-authentication=private

Then run:
% make

Then run:
% make install

On the server side

In the bbftpd directory, run
% ./configure --enable-authentication=private

Then run:
% make

Then run:
% make install

AFS/RFIO64 incompatibility on Linux

On Linux, linking with RFIO64 requires the posix threads library (libpthread). But this library makes the AFS 3.0 authentication routine in the BBFTP server (ka_UserAuthenticate) crash with a segmentation fault. From the client side, you get an error "error reading answer message" because the socket does not exist anymore.

AFS/Globus incompatibility

OpenSSL bug on Linux 2.4

Warning