How You Resolve Security Problems (Linux)
If you are having password or other security/permission problems in Ingres Net, use the following procedure:
1. Verify that you can log in to the remote machine directly. If you cannot, you do not have the right password.
2. Using netutil, re-enter the remote user authorization.
3. If you are running NIS (“yellow pages”), the account’s correct password will be in the yellow pages password file (/etc/yppasswd) rather than in /etc/passwd. Add the following string to the end of /etc/passwd file to tell Ingres Net to look in /etc/yppaswd for the encrypted password:
+::0:0:::
4. If you have additional security such as C2 security enabled on the target machine, you must verify that the ingvalidpw executable exists in $II_SYSTEM/ingres/bin by typing:
$ ls -l $II_SYSTEM/ingres/bin/ingvalidpw
This executable is required to make the password in the secure area readable by Vector.
Note: Not all Vector releases on Linux use ingvalidpw to enforce C2 security. If the ingvalidpw executable is required for your release, it will be documented in the Readme file for your platform.
5. If the ingvalidpw executable exists:
a. Verify that it is owned by root. If not, log in as root and issue the command:
$ chown root ingvalidpw
b. Verify that it has the “set uid” bit set. If not, issue the command:
$ chmod 4711 ingvalidpw
c. Verify that the Vector variable II_SHADOW_PWD is set to the full path to the ingvalidpw executable. Type:
$ ingprenv | grep II_SHADOW_PWD
The ingprenv utility displays the II_SHADOW_PWD variable.
6. If the ingvalidpw executable is not installed, create it using the mkvalidpw script.