Problem
Our documentation suggests using the integrity command to check the system:
http://localhost:8457/en/SEC_admin/ssT.integrity.htmlbut the following problems with integrity have been reported:
After adding a new user, integrity reports:
# integrity -e
/etc/auth/subsystems/audit (entry 47) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/auth (entry 49) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/backup (entry 51) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/cron (entry 53) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/dflt_users (entry 55) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/lp (entry 57) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/mem (entry 59) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/sysadmin (entry 61) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/terminal (entry 63) is wrong.
Owner is root, should be auth.
/etc/auth/subsystems/uucp (entry 65) is wrong.
Owner is root, should be auth.fixmog corrects these problems, but they reappear after adding another new user.
-----And "integrity -e" always resetting the permissions even after a fixmog:
/tcb/bin/integrity -e #-===
system file integrity:
exit status: 1
/.io/bootdisk/boot (entry 38) is wrong.
Group is root, should be backup.
Mode is 0600, should be 0440.
/.io/bootdisk/swap (entry 39) is wrong.
Group is root, should be mem.
Mode is 0600, should be 0440.
/.io/bootdisk/root (entry 40) is wrong.
Group is root, should be backup.
Mode is 0600, should be 0440. Solution
These issues have been reported to SCO Engineering.