Glub Tech, Inc. - Secure FTP Wrapper Frequently Asked Questions

overview

purchase

our clients

download trial

faq

+ del.icio.us

Where is the FAQ for version 2.5? What do I need to run Secure FTP Wrapper? Which clients are supported by Secure FTP Wrapper? Does Secure FTP Wrapper support data encryption? How do I put Secure FTP Wrapper into a debug mode? Does Secure FTP Wrapper work with Microsoft IIS? I have a certificate signed by Verisign, how do I convert the certificate to a format that will work with Secure FTP Wrapper? How can I force only secure connections? Does Secure FTP Wrapper support SSH or SFTP?
Q.	What do I need to run Secure FTP Wrapper?
A.	Secure FTP Wrapper requires the Java 2 Runtime Environment version 1.4 and higher.

Q.	Which clients are supported by Secure FTP Wrapper?
A.	We are aware of five clients that are supported Secure FTP Wrapper by default: our client (Secure FTP), Cute FTP Pro (2.0), FTP Voyager (9.0), FileZilla (1.9.4a), IglooFTP Pro (3.2), and Smart FTP (1.0). But we support any client that can make an Implicit SSL connection (port 990). Starting in version 2.5 the Wrapper can be configured to handle an Explicit SSL connection (AUTH SSL). This feature adds support for WS_FTP Pro (7.5) and NetFinder (2.3.2).

Q.	Does Secure FTP Wrapper support data encryption?
A.	Yes, data encryption is fully supported on all connection types (PASV and PORT).

Q.	How do I put Secure FTP Wrapper into a debug mode?
A.	Edit the file, configuration.xml, and change the numeric value found in the XML block `<log><level>0</level></log>` to a higher number (up to 9). The higher ther number the more verbose the reporting. You will need to restart the wrapper to see the changes.

Q.	Does Secure FTP Wrapper work with Microsoft IIS?
A.	Yes. Secure FTP Wrapper works under Microsoft IIS FTP 5, 6, and 7.

Q.	I have a certificate signed by Verisign, how do I convert the certificate to a format that will work with Secure FTP Wrapper?
A.	Verisign usually sends a certificate in PEM format. The Secure FTP Wrapper 3 supports either PEM or DER format. Note: if you were not given the key/ceritifcate in PEM format but instead have it in one pkcs12 file, then first do the following: Download and install OpenSSL. Getting an RSA private key in PEM format from a pkcs12 file: `openssl pkcs12 -in <verisign.pfx> -nocerts -nodes -out <priv.pem>` Getting an RSA public key in PEM format from a pkcs12 file: `openssl pkcs12 -in <verisign.pfx> -nokeys -out <pub.pem>`

Q.	How can I force only secure connections?
A.	The only way to truly force secure FTP connections would be to firewall off the real FTP port from the outside while letting the wrapper have access to it on the inside. Then have your users talk directly to the wrapper.

Q.	Does Secure FTP Wrapper support SSH or SFTP?
A.	No, we only support FTP over SSL/TLS or FTPS.