VShell(TM) 1.2 (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 1.2.4 (Official) -- May. 28, 2002 --------------------------------------------------- Bug fixes: - 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. - 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. Changes in VShell 1.2.3 (Official) -- Apr. 18, 2002 --------------------------------------------------- Changes: - New icon. 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. Changes in VShell 1.2.2 (Official) -- Feb. 26, 2002 --------------------------------------------------- Changes: - VShell now logs an error if the process exit status is not available after the process exits. Bug fixes: - VShell could send multiple status responses to a SFTP write request if the request failed. - When preparing to execute the shell command, a buffer allocation error could occur. Changes in VShell 1.2.1 (Official) -- Nov. 29, 2001 --------------------------------------------------- Bug fixes: - Due to a race condition in scraper.exe, a crash could occur on dual processor machines when connecting with an SSH Secure Shell version 3.0.0 client. - VShell leaked memory when a connection was disallowed due to a filter or due to name resolution failing. - Due to a bug in NT 4.0, VShell fails to load the system environment when an empty system variable is present. A more precise error message is now generated when this occurs. - Occasionally, VShell would crash because the socket was being cleaned up on the wrong thread. - If VShell failed to read a certificate file, it could cause a crash when used. Changes in VShell 1.2 (Official) -- Oct. 18, 2001 ------------------------------------------------- New features: - Added the registry only option, "Disallow Blank Passwords", which is turned off by default. When this option is turned on, or set to 1, attempted authentications with blank passwords are always rejected. - Added a "-version" command-line option, that displays VShell's version information. Changes: - Added the PID to the "Session Channel Close" log message (if the session channel started a process). - Removed the version log message because it did not display correctly in the Application Event Log and because it can now be obtained by using the "-version" command-line option. Bug fixes: - Under rare circumstances the Control Panel could crash in NT 4 when selecting a domain in the "Select a User or Group" from the Access Control dialog. - VShell could hang if it queued a disconnect packet and the client closed the connection before VShell processed the disconnect. This could happen when a client tried to connect to a VShell server that did not have a host key. - Clients could incorrectly get the error "The SSH2 server does not support password authentication." when connections to VShell failed under any of the following conditions: Change Password Complexity restrictions, Change Password History restrictions, Change Password Length restrictions, or Account Locked. Changes in VShell 1.2 (Beta 4) -- Oct. 11, 2001 ----------------------------------------------- New features: - Added a registry option, "Reveal Version Info", that is turned on by default. If turned off or set to 0, VShell will not report its version string to a connecting client; instead, it will display "SSH-2.0-0.0" as its version string. - Added public-key support for clients conforming to the IETF draft prior to May 2000. This allows clients like SecureCRT 3.0 or OpenSSH 2.1 to connect to VShell using public-key authentication. Changes: - VShell now logs a message when the public-key signature fails. - Added Debug logging for illegal lines received before the IDENT string. - Added debug logging when the IDENT string is received in two different TCP receive operations. Bug fixes: - VShell could have crashed if a hostname or domain connection filter was used and a connection was accepted before the reverse lookup on the prior connection was completed. - VShell may have crashed if a session disconnect occurred during that session's authentication or key re-exchange. - VShell leaked memory while performing the SFTP "setstat" function. - Issuing an "ln" command from the OpenSSH SFTP client caused a session disconnect. - PuTTY clients requesting "tty" mode were disconnected just after connecting because the license nag screen and/or an access denied message was sent before sending a "success" to the PuTTY's shell request message. - The VShell Control Panel could have hard expired before the VShell evaluation did. - Evaluation licenses only allowed two connections instead of ten. - Some port-forwarding log messages were incorrectly logged as connection log messages. - After receiving a quit message, the VShell service would wait for a configuration change, which could have resulted in the service failing to exit cleanly and in a timely manner. - Trusted domains were not shown in the VShell Control Panel's Access Control "Select a user or Group" dialog for NT 4. - Running VShell on a Primary Domain Controller could cause two identical entries to be inserted into the VShell Control Panel's Access Control "Select a user or Group" dialog's combo box. Changes in VShell 1.2 (Beta 3) -- Sept. 19, 2001 ------------------------------------------------ New features: - Added support for an SFTP extension that informs VShell's clients what its new line terminator is. - Added support for an SFTP extension that informs VShell's clients of the available drives and their types. Changes: - Updated SFTP to conform to the latest protocol (version 3). Bug fixes: - Domain user allow and deny rights were ignored when logging on as a domain user using either public key-only or password then followed by public-key authentication. Changes in VShell 1.2 (Beta 2) -- Sept. 14, 2001 ------------------------------------------------ Changes: - Public-key log messages give more specific feedback during public-key authentication. - Added the "session number" to some non-fatal connection and session messages. - Authentication methods are now ordered to list public key before password so that certain older clients could authenticate using public key-only. Bug fixes: - The VShell server temporarily locked up when a user profile took a long time to unload when logging out or when a program like notepad had been left running prior to exiting. - Connecting to VShell 1.2 B1 with a PuTTY client would fail because of an escape sequence being sent to the client before a success response for a shell request was sent. VShell now defers sending the escape sequence until after the success response is sent. - If the thread loading a user's profile wasn't completed while a session was closing (because of a client disconnect), the VShell service could crash (the above PuTTY problem triggered this). - Incorrect (error 317 error 317) was reported if a remote forward failed. VShell now reports the correct error. - A single escape wasn't handled correctly when mouse support was turned on. - VShell no longer counts unauthenticated sessions against the license limits. Changes in VShell 1.2 (Beta 1) -- Sept. 5, 2001 ----------------------------------------------- New features: - Public key-only authentication. - File-based X.509 certificate support allows public-key authentication with smart cards. - Support for OpenSSH-format public keys. - Idle Timeout option allows timing out sessions after a configurable idle time. - Mouse support for character-based applications running in a command window. Changes: - Removed the ability to order ciphers and MACs in VShell - the client determines cipher and MAC preferences. - The VShell evaluation period is now 30 days. Bug fixes: - Made changes to prevent Help dialog from appearing in "Always On Top" mode.