VShell(R) Server 3.8 (Beta) -- May 17, 2011

         Copyright (C) 1995-2011 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
package).


Changes in VShell 3.8 (Beta 5) -- May 17, 2011
----------------------------------------------

No changes.


Changes in VShell 3.8 (Beta 4) -- May 3, 2011
---------------------------------------------

Bug fixes:

  - GSSAPI key exchange could have failed in some cases with a
    protocol error.

  - VRALib: The ITextStream object method ReadUntil() caused a
    crash when used with Visual Basic.


Changes in VShell 3.8 (Beta 3) -- April 12, 2011
------------------------------------------------

Bug fixes:

  - The License wizard could not be started from the VShell
    evaluation dialog.

  - VShell FTPS: Port data connections would not always originate
    from the correct IP on machines that have multiple network
    interfaces or multiple IP addresses.


Changes in VShell 3.8 (Beta 2) -- March 24, 2011
------------------------------------------------

Bug fixes:

  - VShell FTPS: File transfers to the server could have failed
    when an SSL alert packet was of a certain size.

  - UNIX: If the password field in the system shadow file was blank
    for some user, authentication of that user to vshelld could
    still succeed on some systems. 


Changes in VShell 3.8 (Beta 1) -- March 08, 2011
------------------------------------------------

New features:

  - VShell Monitor: New application that allows the VShell
    administrator to view and disconnect active connections to the
    server in real-time.  The VShell Monitor displays username,
    login time, client IP address, protocol, number of bytes
    transferred, and average throughput.

  - Windows: File and folder access permissions can now be set on
    a per user, per virtual root basis.  Permissions include file
    read, write, delete, and folder list, create, and delete.

  - VShell will automatically create a user's Virtual Root path that
    uses the %USER% environment variable when that user connects.

  - Windows: Added registry only option that will force VShell to
    return file listings in UNIX format.

  - Added new trigger parameter that will track the protocol
    (SFTP, SCP, FTPS, FTP) being used for the file operation.

  - VShell FTPS: New option that will require only authentication
    to be encrypted.  All data sent after authentication may be
    unencrypted if this option is used.

  - UNIX: Support for FreeBSD 8.1.

  - UNIX: Support for 32-bit and 64-bit Ubuntu 10.

  - UNIX: Support for 32-bit and 64-bit Red Hat Enterprise Linux
    5.5.

Changes:

  - Windows: Added a button to the VShell Control Panel Common
    page that starts the new VShell Monitor.

  - Windows: Enhanced logging when certificates are used for
    authentication.

  - Windows: IP or netmask connection filters that would allow
    a connection will no longer fail if a later hostname or
    domain name filter fails the required reverse DNS lookup.

  - Windows: If the VShell service experiences a crash, the
    crash dump file will be created in the installation folder.

  - The diffie-hellman-group14-sha1 key-exchange method is now
    enabled by default and is ordered first in the list.

  - Enhanced W3C logging to include the client username, IP
    address, and port in more VShell log messages.

  - UNIX: VShell on Solaris 10 no longer adds the vshelld
    entries to the pam.conf file during installation.

Bug fixes:

  - Windows: VShell Control Panel could crash when adding an
    Active Directory user or group and the security identifier
    could not be resolved.

  - Windows: A connection filter that allowed a specific IP address
    could fail if a later domain or hostname filter failed the
    reverse DNS lookup.

  - VShell could have crashed when a user connected using
    public-key authentication and there was a passphrase protected
    private key in the users public-key folder.

  - The connection limit set in a per user/group subconfiguration
    would only override the main connection limit setting if the
    value of the option was smaller.

  - A user's connection count was not tracked correctly when the
    "Connection Limit" option was specified in a per user/group
    subconfiguration and authentication was canceled.

  - VShell FTPS: The server could have crashed if an
    authentication timeout or idle session timeout occurred at the
    same moment that a user aborted the connection.

  - UNIX: VShell on HP-UX systems would limit the size of uploaded
    files to 2GB.

  - UNIX: VShell could have crashed when run on systems with
    certain Quad-Core AMD processors.