Glub Tech, Inc. - Secure FTP Documentation

overview

purchase

our clients

java web start

documentation

+ del.icio.us

Java Powered

Installation Documentation:

Windows

If you don't have Java 2 (version 1.4 or greater), you must first download and install it.
Download the latest version of Secure FTP.
Double-click the installer.
Follow the installation wizard.

Mac OS X

Download the latest version of Secure FTP.
Unzip the download (if your browser doesn't do it automatically for you).
Mount the virtual drive.
Double-click the installer.
Follow the installation wizard.

Unix

If you don't have Java 2 (version 1.4 or greater), you must first download and install it.
Download the latest version of Secure FTP.
The installer is an executable shell script. From a terminal, run the download as if it were an executable ( sh ./<installer>.bin ).
Follow the installation wizard.

Quick Start Guide

How To Register Secure FTP:

Registration must be done by a privileged account (administrator). To complete the registration, launch Secure FTP and go to Help -> Register Secure FTP. From there, enter the appropriate information and the license code granted from the Glub Tech Store. If you are using the Non-Commercial license, you cannot register the client.

Running Secure FTP 2.5:

Windows

Select the Start menu -> All Programs, and navigate to the Secure FTP 2.5 grouping.
Choose Secure FTP 2.5 to run the version with the graphical user interface (GUI) or Secure FTP 2.5 [CLI] to run the text-based command-line interface (CLI).

Mac OS X

To run the graphical user interface (GUI), go to the install location (most likely /Applications) and double-click on the Secure FTP 2.5 lock icon.
To run the command-line interface (CLI), launch the Terminal program and type ftps at the prompt.

Unix

To run the graphical user interface (GUI), go to the install location and run "sh ./secureftp.sh" at the prompt.
To run the command-line interface (CLI), go to the install location and run "sh ./ftps.sh" at the prompt.
It may be advantageous to put both of these shell scripts in your $PATH to allow for easier access.

Scripting Secure FTP 2.5:

Secure FTP 2.5 supports simple scripting. A script is nothing more than a line-by-line representation of what would be entered at the command line placed in a file. A sample script might look like:

  # Sample Secure FTP 2.5 script
  open ftp.glub.com
  user demo <pass>
  lcd /tmp
  lmkdir test
  lcd test
  cd /pub
  mget *
  quit

To call this script, from the shell command line you would pass in the arguments:

-script <path to script>/<file>

Note: In version 2.5.10 is the ability to have encrypted passwords referenced in your script. To generate an encrypted password, open a terminal/command prompt and change to the Secure FTP installation directory.

From there run:

java -classpath secureftp2.jar com.glub.secureftp.client.cli.EncryptPassword <password>

This will generate some output that will look like ENCRYPTED:xxxxxxxxx. Copy and paste the entire output into the script where the password would go.

Bookmark Converter:

For users of Secure FTP 1.x that have existing bookmarks, an additional utility has been created to ease the transition.

Dowload the jar and save it to the installation directory.
Open a command prompt/shell and change to the installation directory.
Run the following command:
java -jar bookmark_convert.jar

Global Bookmarks:

An option found in the Preferences allows one to specify global bookmarks.

An example of this can be viewed by entering http://secureftp.glub.com/bookmarks.xml into the appropriate preference field and restarting the application.

Overrides:

The following overrides can be made by editing the application's batch/shell script in the following manner:

java -D<override_key>="<override_value>" [rest of commands]

Key	Value	Notes	Product
client.ca	absolute file path	Specify the personal (client) certificate of authority cert (DER/PEM/PKCS#12 formats).	CLI
client.cert.pass	passphrase	Specify the passphrase for the personal (client) key/certificate pair.	CLI
client.private_key	absolute file path	Specify the personal (client) private key (PKCS#8/PKCS#12 formats).	CLI
client.public_cert	absolute file path	Specify the personal (client) public cert (DER/PEM/PKCS#12 formats).	CLI
default.port.ssl.implicit	#	Redefine the default Implicit SSL port [default 990].	CLI
default.port.ssl.explicit	#	Redefine the default Explicit SSL port [default 21].	CLI
forcePasvToUseControlIP	true\|false	Force the passive data transfer to use the same IP as the control channel [default off].	CLI
glub.certficate.generate.keys	#	Redefine the number of days to generate a personal (client) certificate [default 1095].	GUI
glub.dataencrypt.override	true\|false	Force the data channel to be secure by default (breaks spec, but some servers are incorrect in their implementation).	GUI/CLI
glub.debug	true\|false	Enable debug mode.	GUI
glub.default.prompt.no	true\|false	When running a script or interactive mode is off, the default behavior for overwriting existing files.	CLI
glub.errors.ignore	true\|false	Ignore errors that occur when running a script.	CLI
glub.globalurl	URL	Allow for the Global Boomarks URL to be set from outside the preferences.	GUI
glub.resume_xfer.disabled	true\|false	Disable resume transfer option.	GUI/CLI
glub.security.override	true\|false	Ignore security errors at runtime.	CLI
glub.ssl.explicit.only	true\|false	Set the default security of the client to Explicit SSL.	CLI
glub.transfer.force.replace_all	true\|false	Force all data transfers to replace current files (if they exist) without prompting.	GUI
glub.user.dir	absoulte file path	Specify the default local directory.	GUI/CLI
use.jsse	true\|false	Allow for CLI to be run on earlier Java runtime that supports JSSE (v1.2 and v1.3), and the GUI to be run on systems that don't properly support the JRE v1.4 built-in JSSE implementation.	CLI/GUI