|
|
|
Reflection for Secure IT Windows Client 7.0 Service Pack 1 (SP1): Fixes and Features
Technical Note 2376
Last Reviewed 29-Aug-2008
Applies To
Reflection for Secure IT Windows Client version 7.0
Summary
Technical Note 2376
Last Reviewed 29-Aug-2008
Applies To
Reflection for Secure IT Windows Client version 7.0
Summary
Reflection for Secure IT Windows Client 7.0 Service Pack 1 (SP1) is available for maintained customers. This technical note provides information about how to obtain your service pack and a list of features included in SP1.
Note: This content is also available in Japanese at http://docs.attachmate.com/reflection/rsit-ssh/7.0SP1/WinClient/ja/RSITWC7_0_SP1_jpn.pdf.
Note the following:
- This document references a Reflection service pack. Service packs are available to licensed Attachmate customers with current maintenance plans for these products. For information about logins and accessing the Download Library, see Technical Note 0200.
- For a list of fixes originally included in Reflection for Secure IT Windows Client 7.0, see Technical Note 2281.
This note is organized into the following sections:
Obtaining Your Service Pack
Maintained customers are eligible to download the latest product releases from the Attachmate Download Library web site: https://download.attachmate.com/Upgrades/. For more information about logging into and using the Download Library, see Technical Note 0200.
New Features and Fixes in Reflection for Secure IT 7.0 SP1
The following new features and resolved issues are included in the Reflection for Secure IT Windows Client version 7.0 Service Pack 1.
New Features in 7.0 SP1
- Set environment variables on the remote host.
From the Reflection Secure Shell Settings dialog box, click the new Host Data tab. Under Environment variables, click Add to specify a new variable and value. (This change is saved to the Secure Shell configuration file using the SendEnv keyword.)
- Specify one or more commands to execute on the remote server.
From the Reflection Secure Shell Settings dialog box, click the new Host Data tab. Use the Command text box to specify one or more remote commands. Use a semi-colon (;) to separate multiple commands. (This change is saved to the Secure Shell configuration file using the RemoteCommand keyword.)
- Configure ambiguous-width Unicode characters to be displayed as wide characters.
Use the new setting Ambiguous Width Unicode Chars Are Always Displayed as Wide. To configure this, go to Setup > View Settings.
- Configure the client to clear the user name from memory immediately after a connection closes.
Use the new setting Cache Secure Shell User Name. To configure this, go to Setup > View Settings. When this setting is Yes (the default), the user name remains in memory after the client disconnects and users can reconnect without re-entering their user name. The user name remains in memory until Reflection closes and can be seen using the read-only setting Connection Setting UserName. When this setting is No, the user name is cleared from memory when the client disconnects, and users must re-enter their user name for each connection.
Resolved Issues in 7.0 SP1
- The client now continues to transfer the remaining files and folders after a permission denied error occurs during an scp -r transfer.
- Updates have been made to ensure compliance with Section 508 accessibility standards.
- During a rekey exchange, the client now searches for the host key in the global known hosts file in addition to the user-specific known hosts file.
- When an scp -u transfer fails, the source file is no longer removed from the remote host.
- You can now enforce FIPS-approved ciphers and MACs from the ssh command line using ssh -o FipsMode.
- Batch transfers made using the scp and sftp command line utilities no longer fail with a packet too long error when a packet exceeds the expected length.
- Executing multiple, simultaneous scp and sftp batch files no longer results in several rssh.exe processes left running after the scp.exe and sftp.exe processes have completed.
- When an scp -r transfer fails because the folder doesn’t exist, the client now returns an error.
- Users without local administrative rights can now successfully transfer folders containing compressed zip files using the Secure FTP Client.
- The scp command now correctly handles commands that specify a folder name rather than a file name on the command line.
- The client can now import trusted root certificates that contain UTF8 strings. If a parsing error occurs when loading a certificate, the client logs the error and continues running.
- The -k and -o UserKnownHostsFile options now work as expected with the ssh2, sftp2, and scp2 command line utilities.
- The sftp command line utility now warns users when you attempt to rename a file using an existing filename.
- The timestamp is now preserved when you download read-only files from the remote server using scp -p.
- When the ssh command line utility is used with StrictHostKeyChecking set to yes, warning messages for failed connections are now displayed in the command window rather than in a pop-up. This change enables scripts to run without requiring user intervention.
- Transfers made using scp no longer fail when certain Japanese characters are used in the file or folder name.
- The scp2 command line utility no longer requires you to include user@ with the host name.
- Saved changes to terminal window fonts are now preserved correctly for all terminal types.
Supported Platforms in 7.0 SP1
For information about platform support in Reflection for Secure IT, see Technical Note 1944.
