SecureFX geeft de gebruiker een versleuteld SSH2 kanaal waarop bestanden uitgewisseld kunnen worden via SFTP en FTP. Erg handig om toe te passen in verschillende geautomatiseerde omgevingen waardoor je geen belangrijke wachtwoorden in platte tekst over de lijn stuurt. Voor meer informatie over de werking van dit programma wijzen we jullie door naar deze pagina. VanDyke Software heeft de eerste betaversie van 3.1 de deur uitgedaan met de volgende aanpassingen:
- Enhanced support for X.509 certificate authentication.
- Previously, X.509 was supported through a CAPI store. Now, X.509 certificates are also supported directly.
- SecureFX supports forwarding X.509 certificates through the public-key agent. This means that re-authentication is not necessary when connecting to another machine using the same X.509 certificate.
- SecureFX now has an administrator option to run in "FIPS Mode". When this option is set, SecureFX uses a FIPS 140-2 validated cryptographic library and only allow FIPS approved algorithms.
- The Activator supports SSH agent functionality, which means that re-authentication is not necessary if SecureFX is closed as long as the Activator is still running.
- Folders and multiple selected sessions can be connected from the Connect dialog.
- SFXCL: SFXCL now supports /List, which lists the specified directory on the remote system.
- The version information in the About box can now be selected and copied.
- SSH2: Modified the SSH2 page in the Session Options dialog to allow key exchange methods to be configured.
- There was an apparent slowdown when browsing SMB/NetBIOS mounted shares in the Local window.
- If a USB drive was inserted after SecureFX started, it was not displayed in the Local window.
- SSH2: On the SSH2 page in the Session Options dialog, if no key exchange method was selected, the dialog informing that at least one key exchange method must be selected was displayed twice.
- SSH2: Some Kerberos key exchange methods were listed twice in the key-exchange methods list.
- SFXCL: SFXCL crashed if a session that did not have a transfer protocol was specified on the command line.
- SFXCL: If a relative path was specified for the remote and the path did not exist, SFXCL attempted to change directory to an empty path.