Security Considerations

VShell does not change security settings or privilege levels set using normal Windows methods. Only valid users created by an administrator using Windows User Manager or User Manager for Domains will be able to log on to your system through VShell. Users logging on with VShell will have the same privileges as they would have if they directly logged on to the Windows console. For example, if you create a file and deny access to a specific user, VShell will not allow that user to have access to that file.

Unlike many applications that provide remote access by Telnet, when used with one of several available ciphers (such as 3DES or Twofish), VShell does not send passwords in plain text format. Because of this and VShell public-key authentication The process of verifying that an individual truly is who he or she claims to be. Supplying a password is a very common method of authentication. The most secure method of authentication supported in VShell is public-key authentication. Related glossary terms: identity file, public-private key pair , passwords are not exposed to capture during VShell sessions.