Audit Problems on Solaris 8 in BSM mode

Symptoms: SSH Tectia Server is installed on Solaris 8 (SPARC) that is using the Basic Security Module (BSM), but the auditing subsystem cannot see events conducted over the secure shell connection. It may also create a wrong user ID in the crontabs root.au file after the machine has been rebooted.

To ensure that a Solaris host running in BSM-mode is able to audit the SSH Tectia Server events properly and the contents of the crontabs are reliable, SSH Tectia Server must be installed while the Solaris host is NOT in BSM mode. Similarly, when upgrading an existing SSH Tectia Server installation, the Solaris host will need to be in non-BSM mode.

Also, the wrong user ID in the root.au file can be corrected by restarting SSH Tectia Server once after every reboot.

To install SSH Tectia Server on a Solaris host that is NOT in BSM mode, follow these steps:

Uninstall any existing SSH Tectia Server installations according to instructions in Removing from Solaris .
Install the SSH Tectia Server package according to instructions in Installing on Solaris .
Run bsmconv
Reboot the host.
Restart SSH Tectia Server by entering the following command:
```
# /etc/init.d/ssh-server-g3 restart
```
Check that the ssh-server-g3 process, ssh-servant-g3 processes and the auditd process are running.

To install SSH Tectia Server on a Solaris host that is currently in BSM mode, follow these steps:

Run bsmunconv
Reboot the host.
Check that auditd is not running.
Uninstall any existing SSH Tectia Server installations according to instructions in Removing from Solaris .
Install the SSH Tectia Server package according to instructions in Installing on Solaris .
Run bsmconv
Reboot the host.
Restart SSH Tectia Server by entering the following command:
```
# /etc/init.d/ssh-server-g3 restart
```
Check that the ssh-server-g3 process, ssh-servant-g3 processes and the auditd process are running.