Remote & Telnet
VShell Server - Key Benefits
Whether your needs focus on remote access and administration or secure file transfer, the VShell server has a full range of capabilities that enable you to:
- Provide strong, multi-protocol security for data in transit
- Control user access to features and files
- Set up and configure the server easily
- Monitor and log events with automation support
- Tune licensing to your requirements with connection-based editions
Provide strong, multi-protocol security for data in transit. The Secure Shell protocol delivers proven, open-standard authentication, encryption, and data integrity that let you provide a wide range of services to your organization with confidence. Adding FTP over SSL on VShell increases your protocol choices.
Control user access to features and files. VShell gives you extensive controls to manage privileges for shell, file transfer and other services. Examples include access control lists and virtual root directories.
Set up and configure easily. VShell installs and runs right "out of the box". Windows setup and configuration is made easy by the graphical control panel. All platforms support remote configuration.
Monitor and log events with automation support. VShell triggers help you track and respond to events like failed logon attempts and uploaded files. Event logging supports security monitoring and regulatory compliance.
Use connection-based licensing to your advantage. VShell Administrator, Workgroup and Enterprise editions allow cost-effective licensing from one user to thousands. Adding the VShell FTPS edition gives you greater file transfer flexibility. Our support program includes expert technical support and regular maintenance releases.
VShell Server Editions
VShell Server is available in three editions designed to meet the needs of every size network and organization. VShell editions let you control costs by buying only the number of concurrent connections you need. All VShell editions offer the same advanced features. Whether you are the only one accessing a server for administrative tasks or you are providing remote access, secure file transfer, and data tunneling solutions for a large organization with multiple locations, there's a VShell edition that's just right for your needs.
VShell Administrator Server
VShell Administrator Server allows two concurrent client connections, and is designed primarily for remote system administration use.
VShell Workgroup Server
VShell Workgroup Server allows ten concurrent connections, and is intended to serve the needs of a substantial group of users.
VShell Enterprise Server
VShell Enterprise Server supports an unrestricted number of concurrent connections for a large user community.
Changes in VShell 4.3.0
- Windows: Added support for user authentication via an external LDAP server. LDAP users can be granted or denied access to all VShell services, including all file transfer, shell, port forwarding, and remote execute.
- Windows: Streamlined the process of setting up public-key authentication by adding a new interface that allows the administrator to easily view, add, and remove user public keys stored on the server.
- Added support for the firstname.lastname@example.org authenticated encryption cipher.
- Windows: Added an option to limit the total number of concurrent connections allowed to the server.
- Windows: Added a registry only option that allows the administrator to control whether VShell will attempt an interactive logon (Logon Type 2) before a network logon (Logon Type 3). If the option is disabled, VShell will only attempt a network logon.
- Windows: The VShell Control Panel Host Keys page now displays the SHA-2 fingerprint of each host key.
- Added support for the UMAC-128 MAC algorithm.
- UNIX: 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.
- UNIX: The virtual root a connecting user is initially placed in can now be specified. This is useful for users with access to multiple virtual roots with a need to land in a specific one.
- Support added for Windows Server 2016.
- Support added for Ubuntu 16.
- Windows: Added support for multiple backup LDAP servers. If a configured LDAP server is down, VShell will automatically fall back to the next enabled LDAP server. The fall back behavior will only happen when an LDAP server is unreachable.
- Windows: Added an option to control whether VShell will automatically accept and save an SSL certificate sent by an LDAP server.
- VShell now logs disconnect messages received from clients as informational instead of as errors.
- UNIX: Changed the VShell installers to no longer explicitly create the directories where the VShell files will be placed. If the directories do not exist, they will be implicitly created as part of the file copy. This addresses an issue on rpm based platforms (RHEL, CentOS, Suse) in which VShell would be listed as the package owner of these system directories.
- Windows: The base64 encoded SHA-2 fingerprint is now displayed for all host keys on the VShell Control Panel Host Keys page.
- Windows: Added an option that prevents VShell's management provider (WMI) from logging to the Windows Event log. The WMI logging is used for debugging purposes only, so the logging is disabled by default.
- Windows: VShell now performs public-key assistant operations (add, delete, list) in the context of the VShell service account (SYSTEM by default). This avoids needing to set permissions on the public-key folder that could end up being too permissive.
- Windows: The VShell configuration key is now stored in the registry instead of a file to allow for more cluster-friendly operation.
- Windows: The default filename displayed on the host key generation dialog now includes the host key algorithm as part of the name.
- Windows: When adding or editing a virtual root, any forward slashes that appear in the path are now automatically replaced with backslashes. This is to fix an issue where forward slashes were allowed to be entered in the path, but would fail when VShell attempted to resolve the path when a user connected.
- Windows: On the VShell Control Panel Email Server page, increased the space used to display results from sending a test email.
- Windows: Internal user database users that are specified in a Deny Users file are now denied immediately upon connecting. Previously, these users would be allowed to go through the authentication process before being denied.
- VShell FTPS now ignores invalid flags that a client may include as part of a LIST command.
- vsftp/vcp: Because it caused problems for some servers, vsftp and vcp no longer send lstat, stat, or RealPath on "./.".
- vcp/vsh/vsftp: The trace output shows the SHA-2 host key fingerprint as base64 in addition to hexadecimal.
- vkeygen: The SHA-2 fingerprint is now shown in hexadecimal and base64 format when keys are created or displayed using the -l and -f flags.
- vkeygen: The output when vkeygen is run with the -l and -f flags now includes the bit size of the key.
- Windows: The "Use single virtual root" option was not being honored when set via a subconfiguration and the user's virtual root had the home checkbox selected.
- VShell could crash under some circumstances if the deny hosts file in use had the wrong file permissions.
- Windows: When the "Attempt Interactive Logon" registry only option was disabled, subconfiguration files were not loaded for users from the internal user database.
- VShell FTPS was not sending the correct file size for files larger than 4GB when the client used the LIST command for directory listings.
- Windows: Shell connections to VShell running on Windows Server 2016 would sporadically fail with a ReadConsoleOutput error.
- Windows: Unexpected failures could occur if an internal user database file was specified as part of a location subconfiguration.
- Windows: After upgrading from VShell version 2.6 or earlier to version 3.8 or later, access to virtual roots failed due to incorrect file and folder access permissions.
- Windows: When using the Apply button in the VShell Control Panel to save changes, all options were written out to the registry whether they had been changed or not.
- VShell could crash when attempting to add an IP address to a deny hosts file that did not have the correct permissions.
- VShell FTPS could crash if a user disconnected at the same time the connection was closed by the server due to an idle timeout.
- Large file downloads by certain SFTP clients could fail with an insufficient resources error. Added a registry only option ("SFTP Send Queue Byte Limit") that allows administrators to fine tune VShell's allowance for consecutive read requests.
- UNIX: VShell would errantly log a "Lookup failed for child" error after a trigger operation completed.
- vcp/vsftp: Uploading files to a Serv-U SFTP server that only had write permissions in the target directory did not work.
BTSoftware for configuration and implementation support.
This software is subject to export control and may be transmitted, exported, or re-exported only under applicable export laws and restrictions and regulations of the United States Bureau of Export Administration or foreign agencies or authorities. By downloading or using the software, you are agreeing to comply with export controls.
VShell is now available for export to most individuals and organizations worldwide under the Export Administration Regulations (EAR) of the U.S. Bureau of Export Administration (BXA) governing strong encryption software. No restrictions apply to customers located in member states of the European Union (EU) and nine other countries. Restrictions apply to certain government users in other countries.
You will be asked to fill out an eligibility declaration before downloading.Note: In order to use VShell's SSH2 protocol support, you must have use an SSH2 client product like: SecureCRT or SecureFX. Both products work great with VShell.
Perdemia Permission Analyzer available
Reports NTFS permissions
Permission Analyzer jproduct page
Napsys software available through BTSoftware
You can purchase Napsys software through BTSoftware from now on
CopyFlow product page
BTSoftware BV is now official partner of EM Software
BTSoftware BV and EM Software are now partner
BTSoftware BV has partnered with Devart
BTSoftware BV and Devart announce their official partnership.