Kbase P57810: What should permissions be set to for the $DLC/bin directory on Unix?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/11/2006 |
|
Status: Verified
GOAL:
What should the permissions the $DLC/bin directory permissions be set to?
FACT(s) (Environment):
UNIX
FIX:
The Progress executables should have read, write, and setuid for the user. The group and other should also have execute permissions. The owner of the executables should be root. This is accomplished with the the following steps:
1. Log in as root or switch user to root.
2. Move to the $DLC/bin directory.
3. Type the following set of commands:
chown root _*
chmod 4755 _*
chmod 755 _sqlsrv2
chmod 755 _waitfor
An example of what the executables will look like follows.
-rwsr-xr-x 1 root sys 458926 Nov 10 09:49 _mprosrv
-rwsr-xr-x 1 root sys 508210 Nov 10 09:49 _mprshut
-rwsr-xr-x 1 root sys 1450549 Nov 10 09:49 _progres
-rwsr-xr-x 1 root sys 823434 Nov 10 09:49 _proutil
The first column shows permissions for the file:
r - read permission
w - write permission
x - execute permission
s - setuid bit set
The first position tells what kind of file it is. If the file is defined as a normal or unknown file, it has a "-". Other file types are:
d - directory file
l - link file
t - link permission for directories
The next 3 letters are permissions for the user.
The next 3 letters are permissions for the user group.
The next 3 letters are permissions for the other group (all users).
The setuid bit can only be set for the owner and group of the file. The setuid bit allows the user that executes the file to take on the permissions of the owner of the files while running executables. This allows individual users access to the database files while in Progress, but they cannot delete the files when in the UNIX shell.