pmpolsrvconfig -p <policygroupname> [-b][-i <path>][-o][-r <dir>]
[-t sudo|pmpolicy] [-u <policyuser][-w <userpasswd>]
[-g <policygroup>][-l <loggroup>] -s <host> [-b][-q] [-q]
-a <user> [-b][-q] [-q]
-e <host> [-f]
The pmpolsrvconfig program is normally run by pmsrvconfig script, not by the user, to configure or un-configure a primary or secondary policy server. But, you can use it to grant a user access to a repository.
pmpolsrvconfig has the following options.
Table 36: Options: pmpolsrvconfig
Provides the selected user with access to the existing repository. If the user does not exist, it is created. The host must first have been configured as a policy server.
This user will be added to the pmpolicy group to grant it read/write access to the repository files, and to the pmlog group to grant it read access to the log files.
On a secondary policy server, an ssh key will also be generated to provide access to the pmpolicy user account on the primary policy server. The "join" password is required to copy this ssh key to the primary policy server.
Runs the script in batch mode (that is, no user interaction is possible).
Default: Runs in interactive mode.
Unconfigures the policy server, and deletes the repository if this is a primary server.
If you do not specify the -f option, then it prompts you to confirm the action.
|Removes the selected host from the server group.|
Forces the unconfigure action (that is, no user interaction required)
Default: Prompt for confirmation for -x option.
Specifies the policy group ownership for the repository. If this group does not exist, it is created.
Imports the selected policy into the repository. If this is a directory, the entire contents of the directory will be imported.
Specifies the pmlog group ownership for the keystroke and audit logs
Overwrites the repository if it already exists.
Default: Does not overwrite if the repository already exists.
|Configures a primary policy server for the selected group name.|
||Reads the pmpolicy user's password from stdin.|
Creates the repository in the selected directory.
||Configures a secondary policy server. You must supply the primary policy server host name. The secondary policy server retrieves the details of the policy group from the primary policy server. It creates the policygroup and loggroup groups to match those on the primary policy server and configures the policyuser user to grant it ssh access to the repository on the primary server. The "join" password is required to copy this ssh key to the primary policy server.|
Specifies the security policy type: sudo or pmpolicy.
Default: sudo policy type
Specifies the policy user account that manages the production copy. If this user does not exist, it is created and added to both the policygroup and loggroup groups. This user owns the repository on the primary policy server and provides remote access to the repository files to the secondary policy servers.
||Prints the product version.|
(Optional) Sets new user's password for -a option.
Default: No password is configured.
Unconfigures the policy server. If you do not specify the -f option, you are prompted to confirm the action.
This does not remove the repository.
pmremlog -p pmlog|pmreplay|pmlogtxtsearch [-o <outfile>]
pmremlog [-h <host>] [-b] [-c] -- <program args>
The pmremlog command provides a wrapper for the pmlog and pmreplay utilities to access the event (audit) and keystroke (I/O) logs on any server in the policy group. Anyone in the pmlog group can run this utility on the primary policy server.
Note that pmlogtxtsearch is a command located in /opt/quest/libexec.
pmremlog has the following options.
Table 37: Options: pmremlog
||Disables interactive input and uses batch mode.|
||Displays output in CSV, rather than human-readable format.|
|Specifies a host in the policy server group to access.|
|Saves the pmlog output to a file.|
Specifies program to run:
||Displays the Safeguard version number.|
To view the audit log on the primary policy server, enter:
pmremlog -p pmlog -- -f /var/opt/quest/qpm4u/pmevents.db
To view the audit events for user fred on secondary policy server host1, save the pmlog output to a file, and display the result of the pmremlog command in CSV format, enter:
pmremlog -p pmlog -c -o /tmp/events.txt -h host1 -- --user fred
To view the stdout from keystroke log id_host1_x3jfuy, on secondary policy server host1, enter:
pmremlog -p pmreplay -h host1 -- -o -f /var/opt/quest/qpm4u/iologs/id_host1_x3jfuy
To retrieve the contents of keystroke log id_host1_x3jfuy, from secondary policy server host1, formatted for the pmreplay GUI, save the output to a temporary file, and display the result of the pmremlog command in CSV format, enter:
pmremlog -p pmreplay -h host1 -c -o /tmp/replay -- -zz -f /var/opt/quest/qpm4u/iologs/id_host1_x3jfuy
pmreplay -[t|s|i] -[Th] <filename>
pmreplay -[e][I][o] -[EhKTv] <filename>
Use the pmreplay command to replay a log file to review what happened during a specified privileged session. The program can also display the log file in real time.
When using Safeguard for Sudo, enable keystroke logging by configuring the log_input and log_output variables. Please consult your sudoers manual for more information about configuring keystroke logging.
pmreplay can distinguish between old and new log files. If pmreplay detects that a log file has been changed, a message displays to tell you that the integrity of the file cannot be confirmed. This also occurs if you run pmreplay in real time and the Safeguard session that generated the events in the log file is active; that is, the client session has not completed or closed yet. In this case, the message does not necessarily indicate that the file has been tampered with.
The name of the I/O log is a unique filename constructed with the mktemp function using a combination of policy file variables, such as username, command, date, and time.
Safeguard sets the permissions on the I/O log file so that only root and users in the pmlog group can read it. That way, ordinary users cannot examine the contents of the log files. You must be logged in as root or be a member of the pmlog group to use pmreplay on these files. You may want to allow users to use Safeguard to run pmreplay.
By default pmreplay runs in interactive mode. Enter ? to display a list of the interactive commands you can use to navigate through the file.
For example, replay a log file interactively by typing:
the results will show a header similar to this:
Log File : /var/opt/quest/qpm4u/iolog/demo/dan/id_20130221_0855_gJfeP4 Date : 2013/02/21 Time : 08:55:17 Client : email@example.com Agent : firstname.lastname@example.org Command : id Type ’?’ or ’h’ for help
Type ? or h at any time while running in interactive mode to display the list of commands that are available.
pmreplay has the following options.
Table 38: Options: pmreplay
||Dumps the recorded standard error.|
||Includes vi editing sessions when used with -K.|
||When used with -o or -I, prints an optional header line. The header is always printed in interactive mode. |
||Replays the recorded standard input.|
||Dumps the recorded standard input, but converts carriage returns to new lines in order to improve readability.|
||When used with -e, -I, and -o, removes all control characters and excludes vi editing sessions. Use with -E to include vi editing sessions.|
||Dumps the recorded standard output.|
Automatically replays the file in slide show mode.
Use + and - keys to vary the speed of play.
||Replays the file in tail mode, displaying new activity as it occurs.|
||Displays command timestamps.|
||Prints unprintable characters in octal form (\###)|
||Displays the Safeguard version number. |
pmreplay returns these codes:
- 1: File format error – Cannot parse the logfile.
- 2: File access error – Cannot open the logfile for reading
- 4: Usage error – Incorrect parameters were passed on the command line
- 8: Digest error – The contents of the file and the digest in the header do not match
Use the following commands to navigate the log file in interactive mode.
Table 39: Log file navigation shortcuts
||Go to start of file.|
||Go to end of file.|
||Pause or resume replay in slide show mode.|
||Quit the replay.|
||Redraw the log file from start.|
||Skip to next time marker. Allows you to see what happened each second.|
||Display time of an action at any point in the log file.|
||Undo your last action.|
||Display all environment variables in use at the time the log file was created.|
||Go to next position (usually a single character); that is, step forward through the log file.|
||Go to next line.|
||Back up to last position; that is, step backwards through the log file.|
/<Regular Expression> Enter
|Search for a regular expression while in interactive mode.|
Repeat last search.
Display the time of an action at any point in the log file with t, redraw the log file with r, and undo your last action with u.
You can also display all the environment variables which were in use at the time the log file was created using v. Use q or Q to quit pmreplay.
Type any key to continue replaying the I/O log.