UNIX (shell) Commands

The following UNIX (shell) commands are available at your shell prompt when /opt/SUNWicg/SunScreen/bin is included in your $PATH.

• ss_install

• ssadm

• ss_client

  ---

  Note -

  Command equivalents used for the skiptool GUI can be found in the SunScreen SKIP 1.5.1 User's Guide.

  ---

TABLE B-1 lists the SunScreen UNIX (shell) commands and their descriptions. Many of these commands duplicate administration GUI functions, while others provide a context for other commands.

ss_install Command

ss_install is a text-based command-line utility that runs during SunScreen installation to create an initial configuration. ss_install, combined with pkgadd, is the command-line equivalent to the installation-wizard graphical user interface on the CD-ROM.

ss_install interactively queries you with various configuration options, creates a configuration, stores it under the policy name Initial, and activates it.

After ss_install is complete, the Screen is ready to be administered using the administration GUI or the command-line configuration editor and other tools.

ssadm Command

ssadm is the primary command-line tool for SunScreen administration. ssadm has a number of subcommands that perform various operations such as editing and activating a configuration, and examining the status of a Screen.

The UNIX command ssadm provides character-set translation between embedded strings and the local character set of the Solaris system on which it runs.

ssadm runs directly on a locally administered Screen, or indirectly from a remote Administration Station that is using SunScreen SKIP to encrypt IP network communications passing between them. See the SunScreen SKIP User's Guide for more information regarding SKIP encryption.

Usage:

ssadm [-b] [-n] subcommand [parameters...]

ssadm [-b] [-n] -r remotehost [-F ticketfile] subcommand [parameters...]

TABLE B-2 describes the options for this command.

The -b option is normally not needed because the commands that process binary data automatically enable the binary mode. For example, ssadm backup, ssadm restore, ssadm log, ssadm logdump, and ssadm patch handle binary data even if -b is not specified.

The available ssadm subcommands are each described in the ssadm subcommand section of this document.

When ssadm is executed locally on the Screen (that is, without the -r option) no login or authentication is required, but you must be superuser to have any effect.

When ssadm is used with the -r option to access a remote Screen, login authentication is required. You must use the ssadm login command to get a ticket that is used by subsequent invocations of ssadm to allow access to the remote Screen. Normally, the ticket is stored in a ticketfile, the name of which can be specified using the -F option, or through the SSADM_TICKET_FILE environment variable. See the ssadm login command for information about ticket files and remote administration using ssadm.

Executing an ssadm Command From a Local Screen

You can configure a local Screen by typing the commands listed in this appendix using the Screen's keyboard. For example, to activate a policy Initial, you would type:

# ssadm activate Initial

where ssadm is the command you want to execute, activate is the name of the ssadm subcommand, and Initial is the name of the policy you want to activate.

The ssadm command resides in the /opt/SUNWicg/SunScreen/bin directory. Include this directory in your directory search path to have access to the commands on the local Screen.

Executing an ssadm -r Command on a Remote Administration Station

You can configure a Screen from a remote Administration Station by preceding the commands listed in this appendix with ssadm -r and the name of the Screen you want to administer. For example, to activate the policy Initial on a remote Screen called SunScreen1, you would type:

# ssadm -r SunScreen1 activate Initial

where ssadm -r indicates that you want to execute a command on a remote Screen called SunScreen1, activate is the name of the ssadm subcommand, and Initial is the name of the policy you want to activate.

A local ssadm command can be turned into a remote ssadm command by adding -r remote_screen_name immediately after ssadm.

When ssadm is used with the -r option to access a remote Screen, the name of the ticketfile can be specified using the -F option, or through the SSADM_TICKET_FILE environment.