VShell(TM) 2.0 Official -- May 28, 2002 Copyright © 1995-2002 VanDyke Software, Inc. All rights reserved. This file contains a VShell product history. It includes lists of new features, changes, and bug fixes sorted by release. For a product description, installation notes, registration and contact information, please refer to Readme.txt (downloaded with this installation). Changes in VShell 2.0.3 Official -- May 28, 2002 -------------------------------------------------- Bug fixes: - An "Invalid packet header" error was incorrectly thrown during key exchange when a client sent a packet ending with "\r" and a subsequent packet beginning with "\n". - SFTP for OpenSSH and some other clients didn't work because a backward slash "\" was being given at the root instead of a forward slash "/". VShell now presents a forward slash. Changes in VShell 2.0.2 Official -- April 30, 2002 -------------------------------------------------- Bug fixes: - Under Windows NT, ACL entries were repeated in VShell drop down lists in the Control Panel's Access Control or SFTP categories if the network had more than 128 users. - Under Window 2000 and later versions of Windows, trusted domains could not be used in the Access Control Group Picker. - OpenSSH and Putty clients misdetected VShell's version string as another older server. This caused the clients to enable compatibility modes that they should not have, leading to interoperability problems. Changes in VShell 2.0.1 Official -- April 18, 2002 -------------------------------------------------- Changes: - Updated the icon in the License dialog. Bug fixes: - VShell could crash when files with a date prior to January 1, 1970 were uploaded and the client requested that VShell preserve the date/time stamps. - A file's time could be off by one hour on uploads to VShell where the client requested that VShell preserve the date/time stamp. - Corrected mistake on the "Conceal VShell Version Information" help page. Changes in VShell 2.0 Official -- April 2, 2002 ----------------------------------------------- No changes -- Official Changes in VShell 2.0 (Beta 4) -- March 26, 2002 ------------------------------------------------ New features: - Added VKEYGEN.EXE, a new command-line public key generation utility. Changes: - Increased session channel window size to 32K and packet size to 16K to increase file transfer rates. - Disabled key re-exchange for Sun Solaris 9.0 clients because this version does not support key re-exchange. - The certificate mapping page now only displays the local machine certificate store and will give an error about invalid mappings when the Control Panel starts. Bug fixes: - Relinked with the latest zlib compression library, fixing a problem that may manifest itself as a vulnerability that could allow an attacker to conduct a denial-of-service attack, gather information, or execute arbitrary code. For more information see http://www.kb.cert.org/vuls/id/368819 . - When using public-key only authentication, NT groups were added to the user's token, but were not enabled. VShell now sets the correct flags for the NT group attributes. - Some clients would try to stat a drive root without a trailing "\", which would cause VShell to respond with a permission denied error. VShell now appends the trailing backslash if the file ends in a ":", allowing the root to be treated like any other file on the system. Changes in VShell 2.0 (Beta 3) -- March 5, 2002 ----------------------------------------------- No changes -- Release candidate Changes in VShell 2.0 (Beta 2) -- February 21, 2002 --------------------------------------------------- New features: - VShell can now optionally generate first-time host keys automatically after installation in order to facilitate non-interactive enterprise-wide installations. - Added the ability to use %USER% as a root alias in SFTP Root page. On connecting with SFTP clients, VShell expands the variable with the user's logon name. - An SFTP message is logged when files are transferred. The message includes the username, the type of access, and the total bytes transferred. - A message is logged when loading and parsing errors occurred with the certificate map file. Changes: - The apply button is now enabled and disabled based on changes in Control Panel settings. - Multiple users are now allowed to use the same certificate. Previously, only the first user listed in a map file with a given thumbprint was allowed to log on. - The "Remove" button on the SFTP page was always enabled. Now it is disabled if the SFTP Root user list control has the focus. Changes in VShell 2.0 (Beta 1) -- February 5, 2002 -------------------------------------------------- New features: - Support for multiple SFTP Root access points with access control based on NT users and groups. - Improved management of X.509 digital certificates. - Options for fine-tuning the level of X.509 Certificate Revocation Checking (CRL) that VShell performs for each authentication. - Extended Windows platform support by adding Windows XP. - Added an additional key exchange method and improved key exchange configuration and management. - Added the ability to set values for re-exchanging keys in the VShell Control Panel. - Added "Help" and "Apply" buttons to the VShell Control Panel. - Now expand the variable %HOME% in the SFTP Root folder to allow a more flexible root definition for each user. - Pass-through printing allows clients to print output that would normally be printed on the server. - Added an SFTP Logging category in the VShell Control Panel. Changes: - When "Log on Locally" is not granted to a user who is trying to authenticate, the error message is more specific. Bug fixes: - If VShell failed to read a certificate file, it could have caused a crash when used. - VShell caused some clients (specifically, SecureCRT 3.4 and SecureFX 2.0) to hang when disconnecting after authentication timed out. - VShell could have sent multiple status responses to an SFTP write request, if the request failed. - Under Windows XP, VShell did not reload the configuration information after settings were changed. - Environment variables that were defined by using other environment variables were not expanded properly by VShell. - An incorrect error message was given when the user attempted to change a password to be empty. - The incorrect error message "The SSH2 server does not support password authentication" was given for various password failures.