VShell Server Changelog

New in version 4.1.1 Build 862

July 15th, 2015
  • Vulnerabilities:
  • On Mac OS X, VShell FTPS now includes OpenSSL version 1.0.1o which addresses the TLS "Logjam" vulnerability. Please refer to the following pages for details: https://www.openssl.org/news/secadv_20150611.txt https://weakdh.org/
  • Changes:
  • In light of a potential vulnerability with SSH key exchange, similar to the TLS Logjam vulnerability, the diffie-hellman group1 key-exchange algorithm is no longer enabled by default and all 1024 bit primes have been removed from VShell's primes.txt file.

New in version 4.1.0 Build 808 (May 6th, 2015)

  • Bug fixes:
  • UNIX: Files larger than two gigabytes could not be uploaded to VShell on AIX.

New in version 3.9.1 Build 494 (February 11th, 2013)

  • New features:
  • The "Log Topic Debug Level" option can now be specified in a per user, group, or location subconfiguration.
  • Changes:
  • Windows: Restrict the clickable hotspot for several options in the VShell Control Panel to the immediate option text area.
  • Bug fixes:
  • VShell was not displaying the system error text in the log for some file transfer errors.
  • Windows: In some cases, access to virtual roots on network shares was denied.
  • Windows: On the VShell Control Panel Subconfiguration/Location page, the "Config" field was extended so that longer subconfiguration paths can be displayed in full.

New in version 3.8.0 (May 19th, 2011)

  • 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.

New in version 3.6.6 (April 27th, 2011)

  • Bug fixes:
  • 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.
  • VShell FTPS: File transfers to the server could have failed when an SSL alert packet was of a certain size.

New in version 3.6.0 (December 14th, 2009)

  • Limit user access to SSH2 commands and services using the public key:
  • New support for public key "private use" headers allows admins to restrict users to commands or subsystems through the key.