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 tweede betaversie van 3.1 de deur uitgedaan met de volgende aanpassingen:
SecureFX® 3.1 (beta 2) complies with FIPS 140-2 cryptography requirements, offers improved authentication with X.509 digital certificates, adds the ability to easily launch multiple sessions, and improves SSH agent functionality.
New features:Changes:
- SSH2: Passwords for SSH2 sessions can be changed from the Session Options dialog using the SSH2 protocol when it is supported by the remote machine.
Bug fixes:
- When "FIPS mode" is enabled, invalid cryptographic algorithms are not displayed in the Session Options dialog.
- When "FIPS Mode" is enabled, FTP one-time password support is disabled.
- When "FIPS Mode" is enabled, it is displayed in the About box.
- SSH2: Added default support for X.509 certificate server host keys.
- SSH2: When a key exchange method is not supported, a message is logged to the trace output.
- SSH2: Authentication methods can be edited in the Session Options dialog for SSH2 sessions that are connected.
- SecureFX crashed when copying a file on the remote machine to a new location on the same remote machine.
- If a file was uploaded to a file that already existed on the remote machine and the new file was smaller than the existing file, the uploaded file contained the tail end of the old file.
- SecureFX crashed when remotely editing an ASCII file on a UNIX or Linux server.
- When SecureFX and SecureCRT were integrated and the terminal protocol for a session was set to SSH2 and the transfer protocol was set to FTP, if the password was saved, it had to be re-entered when switching between SecureFX and SecureCRT.
- SSH2: Pressing OK in the GSSAPI Properties dialog caused SecureFX to crash
- SSH2: When compression was on, key exchange failed during connection because SecureFX did not send the correct list of compressions.
- SSH2: When "FIPS Mode" was enabled, the New Host Key dialog did not display the server's fingerprint. It is now displayed as a SHA-1 hash when "FIPS Mode" is enabled.
- SFXCL: The /List command in SFXCL crashed after the command was executed.
:strip_exif()/i/1200421188.gif?f=thumbmedium)