Summary of Shell Script Behavior in the Trusted Solaris Environment

• If none of its commands need privileges, a shell script can be created by anyone who is permitted to use a text editor.

• A shell script can used by anyone who has access to the script and its interpreting shell.

• Forced privilege shell scripts do not pass privileges to commands that they contain.

• Allowed privileges on shell scripts have no effect on which privileges the programs executed by the shell script can use.

  The allowed privilege set of the invoked shell's file is checked rather than that of the script's file.

• Standard shell scripts do not use the rights profile mechanism.

• A standard shell script that is invoked in a profile shell can pass privileges to commands that it runs if the Security Administrator role lists the shell script with any privileges required by its commands in one of the invoking account's profiles.

  The shell script can pass any of its inheritable privileges to the commands it executes if the commands' executables have the allowed privileges. Because the commands are being run in a standard shell, it is no use to list them with privileges in one of the invoking account's profiles. The following figure shows a standard script executing in a profile shell.

Figure 13-3 How Shell Scripts Pass Inheritable Privileges Using a Profile Shell

• Profile shell scripts, that is, scripts that begin with the line #!/bin/pfsh|ksh|sh, can pass privileges to their commands in whatever shell they are running. The commands must be listed with the required privileges in one of the invoking account's profiles.