VShell Aims to Harden Security With 3.6 Release

After five beta releases, VanDyke Software’s VShell 3.6 Secure Shell Server 3.6 is gold. Key new features in Windows and Unix, include:

• X-command and X-subsystem private use headers in public-key
  files are now supported. This provides the ability to restrict
  a user to a particular command or subsystem when a specific
  public key is used for authentication.
• Environment variables can now be set via the SSH2 protocol.

After five beta releases, VanDyke Software’s telnet server, VShell Server 3.6, got the gold stamp of approval.

In Windows:

• The 64-bit version of VShell now uses a FIPS 140-2
  validated cryptographic library.
• VShell internal user database users can now connect
  using public-key authentication.
• When using x.509 certificate authentication, the User
  Principal Name can now be retrieved from the certificate’s
  Subject Alternative Name field.
• Option to only load user profiles that are set to local.

Complete release notes are available, here, and the full text of the press release can be found below.

VShell 3.6 server from VanDyke Software, helps organizations transfer files and secure data with fine-grained access control and configuration options. The 3.6 release announced today provides new controls over user access to commands and subsystems through public key “private use” headers.

“With the complexity of network environments, system administrators want Secure Shell servers with more control over end-user access to files and services,” said Jeff P. Van Dyke, President of VanDyke Software. “VShell 3.6 provides that by allowing admins to restrict users to commands or subsystems through the same public key that authenticates the user.”

VShell 3.6 also improves back-end control with the ability to set environment variables with SSH2 on the Windows server and expands logging capability for UNIX and Linux versions.

Read the Full Story

Follow ServerWatch on Twitter