PRODUCTS > VSHELL
Send us a question or comment

VSHELLD

Section: Maintenance Commands (8)
Updated: Version 3.8

 

NAME

vshelld - VanDyke Software Secure Shell server daemon  

SYNOPSIS

vshelld [-debug][-f config-file]
vshelld [-version]
vshelld [-test_config]  

DESCRIPTION

vshelld (VShell(R) for UNIX) lets you replace nonsecure Telnet and FTP servers with secure remote access to UNIX systems. vshelld , which uses the SSH2(TM) protocol, provides strong data encryption and multiple authentication options using password and public-key authentication. Port forwarding with vshelld allows you to secure existing TCP/IP application data without major changes.  

OPTIONS

Command-line options are described below.
-debug
Specifies "debug" mode. When run with this option, vshelld runs in the foreground and sends trace output to the stderr. In debug mode, vshelld will handle one connection and exits when that connection closes.
-f config-file
Use the specfied configuration file.
-t or -test_config
Specifies "test" mode. When run with this option, vshelld tests the configuration file and reports any errors, warnings, or if the file is valid. This option only verfies the file and will not start the vshelld server. This option cannot be used at the same time as -debug.
-version
Outputs the version information and exits.
 

FILES

The following are the locations of the configuration and other data files.
Configuration file (vshelld_config)
By default, this file is located in /usr/local/etc. Alternatively, the path can be specified on the command line.
Host key files (vshelld_hostkey and vshelld_hostkey.pub)
The path of the private host key file is specified in vshelld_config(5). If the path is not specified in the configuration file, the path {{VSHELLD_HOSTKEY_PATH}} will be used.
Public key file
The directory of this file is specified in the configuration file. By default, the location is $HOME/.vshell/publickey. The options below can be specified in the header of a public key to restrict the user of that public key to a specific command or subsystem.

  To restrict the user to the specified subsystem, use the 
  following:
    X-Subsystem: <subsystem name>

  To restrict the user to the specified command, use the 
  following:
    X-Command: <command name>
Group exchange primes file (primes.txt)
In order to use Diffie-Hellman group exchange, a file containing a list of primes is required. This file should be located in the same directory as the configuration file.
vshelld.pid
On startup, vshelld writes its process ID to the file {{VSHELLD_PID_PATH}}. The name of this file can be configured in vshelld_config(5).
~/.vshellrc
This file , located in each user's home directory, contains user-specified settings. The following settings are supported:
   umask - Sets the default umask on all uploaded 
           files.  For example, adding the follow-
           ing line to the .vshellrc file will set
           the default umask on all uploaded files
           to 022 instead of 077 (the   vshelld
           default) and will mask off the write 
           bit for "group" and "other":
           
             umask 022
   lang -  Specifies the lang that should be used 
           for SFTP files; this option is used in 
           place of executing the user's "dot" 
           files because of the security issues of 
           executing files with arbitrary content.
           This field can be set to any valid value
           for the LANG environment variable. 
           
           For example:
             lang en_US.UTF-8
           or
             lang ja_JP.UTF-8
           Where the system supports it, it is 
           suggested that the UTF-8 character set 
           be used, as this character set supports 
           display of multiple languages.
 
 

SIGNALS

vshelld reacts to some signals. The file {{VSHELLD_PID_PATH}} can be used to send a signal to vshelld , for example:
     kill -SIGHUP `cat {{VSHELLD_PID_PATH}}`
SIGHUP
Causes vshelld to re-read its configuration file and re-load the primes in the primes.txt file.
SIGTERM
Causes vshelld to exit.
 

ENTERING LICENSE DATA

To enter your vshelld license data, complete the following steps:
1. Create a plain text file called vshelld.lic in the {{VSHELLD_CONFIG_PATH}} directory where the vshelld configuration information is located. If the -f <path> option is used when starting VShell, the license file must be located in the path specified. For a license with serial number SERIAL, this file should include the following lines:
   Name: NAME
   Company: COMPANY
   Serial Number: SERIAL
   Key: KEY
   Issue Date: DATE
2. Enter the data exactly as shown. If your license data has an empty Name or Company field, leave the corresponding field in vshelld.lic blank.
3. Restart VShell for UNIX. The licensing reminder should no longer be displayed at start up. If you have any problems with your key or have other product questions, please email vshell-questions@vandyke.com.  

SEE ALSO

vcp(1), vkeygen(1), vpka(1), vsftp(1), vsh(1), vshelld_config(5)

 

COPYRIGHT

Copyright (C) 1995 - VanDyke Software, Inc.

VanDyke Software and VShell are trademarks of VanDyke Software, Inc. All other products and services mentioned are trademarks or registered trademarks of their respective companies.


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
FILES
SIGNALS
ENTERING LICENSE DATA
SEE ALSO
COPYRIGHT