Converse agora com nosso suporte
Chat com o suporte

Privilege Manager for Unix 7.2.3 - Administration Guide

Introducing Privilege Manager for Unix Planning Deployment Installation and Configuration Upgrade Privilege Manager for Unix System Administration Managing Security Policy The Privilege Manager for Unix Security Policy Advanced Privilege Manager for Unix Configuration Administering Log and Keystroke Files InTrust Plug-in for Privilege Manager for Unix Troubleshooting Privilege Manager for Unix Policy File Components Privilege Manager for Unix Variables
Variable names Variable scope Global input variables Global output variables Global event log variables PM settings variables
Privilege Manager for Unix Flow Control Statements Privilege Manager for Unix Built-in Functions and Procedures
Environment functions Hash table functions Input and output functions LDAP functions LDAP API example List functions Miscellaneous functions Password functions Remote access functions String functions User information functions Authentication Services functions
Privilege Manager for Unix programs Installation Packages

pmmasterd

Syntax
pmmasterd [ -z on|off[:<pid>] ] [ -v ]| [ [ -ars ] [ -e <logfile> ] ]
Description

The Privilege Manager for Unix master daemon (pmmasterd) is the policy server decision-maker. pmmasterd receives requests from pmrun or the Sudo Plugin and evaluates them according to the security policy. If the request is accepted, pmmasterd asks pmlocald or the Sudo Plugin to run the request in a controlled account such as root.

A connection is maintained between pmmasterd and the Sudo Plugin for the duration of the session. This also occurs between pmmasterd and pmlocald, if keystroke logging is enabled. When the pmmasterd connection is maintained throughout the session, keystroke and event log data is forwarded on this connection.

If keystroke logging is not enabled, pmlocald reconnects to pmmasterd at the end of the session to write the event log record showing the final completion code for the command run by pmlocald. If pmlocald is unable to reconnect, it writes instead to a holding file, pm.eventhold.hostname. It then attempts to write the pmevents.db record to the host the next time pmmasterd connects to pmlocald. Multiple files can accrue and they will all be delivered to the proper host when the connection is restored.

The policy server master daemon typically resides on a secure machine. You can have more than one policy server master daemon on different hosts for redundancy or to serve multiple networks.

pmmasterd logs all errors in a log file if you specify the -e filename option.

Options

pmmasterd has the following options.

Table 72: Options: pmmasterd
Option Description
-a Sends job acceptance messages to syslog.
-e <filename> Logs any policy server master daemon errors in the file specified.
-r Sends job rejection messages to syslog.
-s Sends any policy server master daemon errors to syslog.
-v Displays the version number of pmmasterd and exits.

-z

Enables or disables tracing for this program and optionally for a currently running process.

Refer to Enabling program-level tracing before using this option.

Files
  • Privilege Manager for Unix policy file (pmpolicy type): /etc/opt/quest/qpm4u/policy/pm.conf
Related Topics

pmcheck

pmkey

pmlocald

pmpasswd

pmreplay

pmrun

pmsum

pmmg

Syntax
pmmg /<full_path_name>
Description

The pmmg text editor is a special version of the mg text editor that you can use securely with Privilege Manager for Unix programs; it is a small version of gnu emacs with gnu-style emacs key bindings. You must specify a full pathname as an argument when starting pmmg. Also, you will not be able to access any files other than the ones you specified at startup time. Nor will you be allowed to spawn any processes.

When you the pmmg program with Privilege Manager for Unix, it allows you to access a specific file as root, but not other root functions.

pmpasswd

Syntax
pmpasswd
Description

The pmpasswd program generates an encrypted password which can be used in a custom configuration script. When you type pmpasswd, it asks you to type the password twice, then prints out the encrypted version. You can use the encrypted version as the first argument to the getstringpasswd function in the configuration file.

Related Topics

getstringpasswd

pmpolicy

Syntax
pmpolicy -v | -z on|off[:<pid>] command [args] [-c] [<command>.] -h
Description

pmpolicy is a command line utility for managing the Privilege Manager for Unix security policy. Use the pmpolicy command to view and edit the policy in use by the group. Any user in the pmpolicy group may run this command on any configured policy server host.

This utility checks out the current version, checks in an updated version, and reports on the repository.

You can use the -c option to display the result of the command in CSV, rather than in a human-readable form. The CVS output displays the following fields: Resultcode, name, description, Output msg.

The pmpolicy utility exits with the following possible exit status codes, unless otherwise stated below:

Exit status codes
  • 0: Success
  • 1: Repository does not exist
  • 2: Specified path does not exist
  • 3: Failed to checkout from the repository
  • 4: Failed to check in to the repository
  • 5: Syntax error found in new policy – check in was abandoned
  • 6: Conflict found when attempting a check in - check in was abandoned
  • 7: Policy type not found in repository
  • 8: Failed to access the repository to report requested information
  • 9: The selected version was not found in the repository
  • 10: Directory did not contain a working copy
  • 11: Check in abandoned
  • 12: Invalid path specified
  • 13: Invalid configuration
Options

The following is a summary of the commands and options available to pmpolicy.

Run any command with a -h to get more information about it. For example: 

pmpolicy <command> -h
Table 73: Commands and options: pmpolicy
Command Description
add Adds a new file from the specified path to the policy repository. 
add -p path -d dir [-n [-l commitmsg]] [-c] [-u <user>]

Records the addition of a new file to the working copy of the policy. Use the -p option to specify the file path (relative to the top-level directory in the policy) to add. Use the -d option to specify the directory of the working copy. The -n option commits the changes to the repository. If you use the -n option, you can also use the -l option to provide a commit log message. If you use -n without the -l, the command interactively prompts you for the commit log message

checkout Checks out a working copy of the policy to the specified directory. 
checkout -d <dir> [-c] [-r <revision>]

If the directory does not exist, it is created. If the selected directory exists, the existing contents is overwritten. By default, the latest copy is retrieved; use the -r option to check out a particular revision. You can specify a revision using SVN DATE format, or the HEAD keyword, as well as revision numbers.

A date format specified without a time, defaults to 00:00:00.

The earliest time you can use to identify a particular revision is one second after the time you commit the revision. For example, if you committed revision 2 at 12:00:00, then you must specify a time of 12:00:01 or later to check out revision 2. For example:

pmpolicy checkout -d /tmp -r "{2012-01-02 12:00:01}" # checkout revision that existed on 2012-01-02 00:00:00
commit Checks in changes from a working copy to the policy repository. 
commit -d <dir> [-l <commitmsg>] [-c] [-a force|abort|merge|overwrite][-u <user>]

Commits the working copy of the policy from the indicated directory. All files in the indicated directory are checked in to the repository.

This working copy is first verified for syntax errors using the pmcheck utility. The working copy must match the policy type currently in use, otherwise a syntax error will be produced by pmcheck.

If no syntax errors are encountered, it attempts to check in this copy into the repository, honoring the -a option as described below. Exit status of 0 indicates successful check in.

The -a option indicates the action to be taken when checking in a working copy, if the repository has changed since the working copy was checked out, that is, the edits are based on an out-of-date copy of the repository. The resulting differences between the working copy and the repository may or may not conflict.

You can specify the following actions:

  • Merge: If the only differences are non-conflicting, then merge the changes. If any conflicting changes are found, abort the check in.
  • Overwrite: Merge the changes. If any conflicting changes are found in the repository, select those from the working copy.
  • Force: Overwrite the copy in the repository with the working copy, discarding any changes that have been committed since the working copy was checked out.
  • Abort: Abandon the check in if the working copy is out of date, regardless of whether changes are in conflict (this is the default)

For example:

pmpolicy commit -d /tmp -a force
diff Checks the differences between two revisions of the policy and reports the output to stdout, or to the selected output file. 
diff [-o <outfile>][-c][-f][-p <path>][-d <dir> [-r <v1>]] | [-r [<v1>:[<v2>]]

By default, this option displays the differences between the two selected revisions. If you specify the -f option, it displays the incremental differences between each revision in the specified range. You can specify revisions using any acceptable SVN revision format, such as HEAD, COMMITTED, or DATE format. You can use the -o option to report the "diff" output to a file, rather than to stdout (the default).

  • If you specify a directory, it compares the copy in that directory with the selected revision (or the latest revision in the repository, if you do not specify a revision).
  • If you specify one revision, it reports the difference between the latest and selected revision.
  • If you specify two revisions, it reports the difference between the selected revisions.

Exit status codes:

  • 0: no differences were detected.
  • 1: differences were detected
  • 2: An error occurred

For example:

pmpolicy diff -d /tmp -o /tmp/diffs.txt -r2 pmpolicy diff -r1:2 -o /tmp/diffs.txt
edit

The utility checks out a temporary working copy of the policy and starts the appropriate interactive editor to edit the files. 

edit [-a force|abort|merge|overwrite] [-l <commitmsg>] [-p <path>][-u <user>]

This option is useful for manual interactive editing of the policy on the command line.

On completion of the edit, it verifies the syntax of the policy. If no errors are found, it checks the edits back in to the repository. If any errors are found, then it exits without checking in the changes.

When saving an edited policy, some non-ASCII characters in the commit log message may error and cause all changes to the policy to be discarded. To avoid this possibility, avoid using backspace, arrow keys and any other keys that may be interpreted as non-ASCII characters within the shell.

help Displays usage information.
log Logs revision information about the repository. 
log [-o <outfile>][-c][-e][-r <revision>]

Reports information about the repository to stdout or to the selected output file. This displays details of the user who changed the repository, the version number for this change, along with the time and date of the change.

By default, this option shows details of each revision in the repository, one version per line. If you specify a version, it shows the details of this version. You can use the -o option to report the "log" output to a file, rather than to stdout.

The status is displayed in the following format for CSV output:

"<version>","<username>",<YYYY-MM-DD>,<HH:MM:SS>"<commitmsg>"

For example:

pmpolicy log -r 3
masterstatus Reports the status of the production copy of the policy used by Privilege Manager for Unix to authorize commands. 
masterstatus [-o <outfile>] [-c]

The production copy is stored in the following directory by default: 

/etc/opt/quest/qpm4u/policy/

You can use the -o option to report the information to a file instead of to stdout.

It reports the following information:

  • Path to the production copy
  • Date and time the production copy was checked out
  • Revision number of the production copy
  • Latest trunk revision number of the repository
  • Locally modified flag (indicates that someone manually edited the file)

The information is displayed in the following format for CSV output:

<path>,<YYYY/MM/DD>,<HH:MM><policyrevision>,<trunkrevision>,0|1
remove

Removes a file from the specified path in the policy repository. 

remove -p path -d dir [-n [-l <commitmsg>]] [-c] [-u <user>]

Removes a file from the indicated working copy directory. Use the -p option to specify a path to the file (relative to the top-level directory in the policy). Use the -d option to specify the directory of the working copy. The -n option commits the changes to the repository. If you use the -n option, you can also use the -l option to provide a commit log message. If you use -n without -l, the command interactively prompts you for the commit log message.

revert Reverts to the selected revision of the policy.
revert [-c] [-r <version>][-l <commitmsg>]

Checks out a copy of the selected revision, edits the files, and checks the copy back in as the latest revision.

status Verifies the working copy of the policy in the directory indicated. 
status -d <dir> [-c]

Verifies the working copy of the policy in the specified directory. You can use this to verify the status of a working copy that was previously checked out, before attempting to commit any edits. Each file in the selected directory is checked against the latest version in the repository. For example:

pmpolicy status -d /tmp

Exit status codes:

  • 0: The working copy is up to date and has not been modified; no action is required.
  • 1: The working copy is up to date and has been modified; you must check in to commit the edits made in the working copy.

    To commit the changes, run:

    pmpolicy commit -d <dir>

  • 2: The working copy is out of date and has not been modified; You must check out to get an up-to-date copy of the policy before editing.

    To check out the latest copy, run:

    pmpolicy checkout -d <dir>

  • 3: The working copy is out of date and has been modified, but the changes do not conflict with the latest version. Therefore, a default check in will fail. To commit the you must use the -a option.

    To commit the changes, run:

    pmpolicy commit -d <dir> -a merge

  • 4: The working copy is out of date and has been modified and the changes conflict with the latest version, therefore a default check in will fail.

    To commit the changes and overwrite any conflicts with the working copy’s changes run:

    pmpolicy commit -d <dir> -a force

  • 5: An error occurred when attempting to verify the status.

sync Checks out the latest version to the production copy of the policy used by Privilege Manager for Unix to authorize commands. 
sync [-f][-c]

Synchronize the local production copy of the policy with the latest revision in the repository.

-v Displays the Privilege Manager for Unix version.

-z

Enables or disables debug tracing and optionally sends SIGHUP to a running process.

Refer to Enabling program-level tracing before using this option.

Related Topics

pmcheck

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação