S4Software Home  
Contact
Search
Home About Us Products Services Partners Events  
 

Secure4Privilege (suGUARD) FAQ

Installation

Does the system have to be rebooted after Secure4Privilege is installed?

What if a previous version of Secure4Privilege is already installed?

When attempting to run the installation script, I received the following error: "The Secure4Privilege installation script must be run from the root account". I did a su to root before attempting to run the script so why won't it let me continue?

Menu Program

What are the keys used in the character-based menu program ('Execute', 'Next page', etc.)?

I tried to run the menu program, but I received the following error: 'You do not have the privileges needed to run this program'. I was root at the time so why could I not run the menu program.?

I logged in to my workstation as root and tried once again to run the menu program. Now I get the following error: 'Secure4Privilege has expired...' but I just installed it!

The GUI doesn't start; the character-based version comes up instead. Why?

I tried to bring up the menu, but I got an error message and the system did a core dump. The error said, 'Warning locale not supported by xlib. Locale set to C. X local modifiers not supported.' What went wrong?

Trying to start the GUI version yields many, many errors, finally comes up in black and white. Why?

The GUI appears to be hung up, mouse clicks on main menu bar don't work, etc.

The error message appears "Error, database could not be opened" but the GUI seems to come up normally.

I get a lot of key translation errors appearing before the GUI starts on Solaris.

I had a few key translation errors appear, e.g. 'Warning: Cannot convert string "<key>InsertChar." to type Virtual Binding'.

Why does the user keep getting shell prompts when running the character-based version of the menu program?

Are there any commands that should not be installed in Secure4Privilege?

Contact Support

How do I contact technical support?

Installation

Does the system have to be rebooted after Secure4Privilege is installed?

No! Secure4Privilege can be installed on the system, without taking it down, without requiring users to log out - basically without a hassle. There is no need to reboot after Secure4Privilege is installed either. Secure4Privilege does not modify the kernel.

What if a previous version of Secure4Privilege is already installed?

In general, new versions are distinguished by increments in the tenth digit (e.g. 2.0, 2.1) and are installed in separate directories. Updates are distinguished by increments in the hundredths digit and are installed in the same directory (e.g. 2.01 and 2.02 are minor updates and would be installed in the /bin/secure4/s4priv_2.0 directory).

Before beginning a minor upgrade to an existing version of Secure4Privilege, the network daemon (s4privnet) needs to be taken down. If this is not done prior to beginning the installation, the installation script will abort. The installation script will make a backup copy of the current version of Secure4Privilege before beginning the new installation.

When attempting to run the installation script, I received the following error: "The Secure4Privilege installation script must be run from the root account". I did a su to root before attempting to run the script so why won't it let me continue?

You must be directly logged into the system as root, not as a non-root account. The script looks at the originating UID to determine privileges.

Menu Program

What are the keys used in the character-based menu program ('Execute', 'Next page', etc.)?

Key mappings vary depending upon the type of terminal being used. Depending upon the keyboard configuration, these functions can be invoked by using function keys, or special keyboard characters. The following table outlines the various key mappings for commonly used terminals.
Standard Keys and Functions

Click here for keys table

I tried to run the menu program, but I received the following error: 'You do not have the privileges needed to run this program'. I was root at the time so why could I not run the menu program?

Most likely you were logged in to the system with your own id then did an su to root. In order to run the main menu program, the user's initial login account must have a valid account profile with proper management privileges, and the effective UID must be 0 (root). The software release directory contains a profile for the root account, which enables root to run the menu program. While running the menu as root the first time, your account profile should be created with proper management privileges to enable you to login to the system, su to root, then run the menu program.

I logged in to my workstation as root and tried once again to run the menu program. Now I get the following error: 'Secure4Privilege has expired...' but I just installed it!

Demo copies of Secure4Privilege comes with a temporary set of keys that are pre-expired. Use the command /bin/secure4/s4privmgr -v to get the primary reset codes.

Forward these codes to S4Software by calling (619) 574-5375 or by sending email to support@s4software.com.

The GUI doesn't start; the character-based version comes up instead. Why?

The user's DISPLAY environment variable is not set.
Set the DISPLAY environment variable or invoke s4privmgr using the -display switch. /bin/secure4/s4privmgr -display <hostname>:0.0

I tried to bring up the menu, but I got an error message and the system did a core dump. The error said, 'Warning locale not supported by xlib. Locale set to C. X local modifiers not supported.' What went wrong?

You probably tried to start the GUI version of the menu program directly (entering s4privmgrX). This problem should not occur if the GUI is started using the s4privmgr script. If you wish to start s4privmgrX directly, it requires that the environment variable XNLSPATH be set. If the target system does not have a nls directory, XNLSPATH can be set to
/bin/secure4/nls.
You may wish to include this setting in the appropriate login file(s).

Trying to start the GUI version yields many, many errors, finally comes up in black and white. Why?

Some other program (e.g. the Netscape browser) is using the color map. That program will have to be terminated to enable the color version of Secure4Privilege to run.

The GUI appears to be hung up, mouse clicks on main menu bar don't work, etc.

There is a Secure4Privilege window that is requesting a selection, confirmation, etc. Look around for it - it may be hiding behind another window.

This problem sometimes arises because of the window selection policy. Change the mouse behavior so windows activate automatically.

The error message appears "Error, database could not be opened" but the GUI seems to come up normally.

The database in question is the help database. You will find pressing 'F1' or the help buttons does not bring up help information. Normally the user should invoke Secure4Privilege by doing a cd to /bin/secure4 then invoking s4privmgr. The Motif tool issued for the GUI does not use environment variables or follow the path to find the help file. It must find it in the current directory. If the user wants to invoke Secure4Privilege from some other directory, move to the directory where they wish to invoke Secure4Privilege and create a link to the help database as follows:

ln -s /bin/secure4/s4priv.dir/s4privmgrX.ehdb <linkname>

I get a lot of key translation errors appearing before the GUI starts on Solaris.

Solaris does not have the XKeysymDB file in the standard directory. The following link should be created:

ln -s /usr/openwin/lib/XKeysymDB /usr/lib/X11/XKeysymDB

Note that it may first be necessary to create the directory /usr/lib/X11.

I had a few key translation errors appear, e.g. 'Warning: Cannot convert string "<key>InsertChar." to type Virtual Binding'.

Sometimes the XKeysymDB does not have entries for items like 'DeleteChar'. These are included in the file /bin/secure4/XKeysymDB. This file can be appended to the system's XKeysymDB file, by following the directions in the file.

WARNING: Do NOT replace the system's XKeysymDB file with the one provided by Secure4Privilege! The version in the secure4 directory includes only four entries. Append the Secure4Privilege file to the existing one.

Why does the user keep getting shell prompts when running the character-based version of the menu program?

The <Tab> key has been used to move between fields. The <Tab> key starts a shell process.

Type exit to return to the menu program. Change the shell key, if necessary, by using the configuration file option shellkey described in Appendix A of the Secure4Privilege Reference Manual.

Are there any commands that should not be installed in Secure4Privilege?

Following is a list of commands that should not be placed under Secure4Privilege control:

cat, lp, more, ps, s4privrun, xterm

The alarm script defined by the alarm configuration option.

Contact Support

Contacting S4Software for technical assistance:
S4Software can be contacted by calling (619) 574-5375 (8:00 a.m. to 5:00 p.m. US Pacific Time)
Or by sending email to support@s4software.com


 
Contact Support
S4Access Support FAQ
S4Audit Support FAQ
Support Plans