User's Manual

Solaris 9 Security CX-310-301 33
Note: A reboot of the system automatically causes the current log file to close and a new one to be opened
when the system comes back up.
Disabling BSM
If you no longer want to run the auditing facility it can be easily disabled by running:
# /etc/security/bsmunconv
bsmunconv: ERROR: this script should be run at run level 1.
Are you sure you want to continue? [y/n] y
This script is used to disable the Basic Security Module (BSM).
Shall we continue the reversion to a non-BSM system now? [y/n] y
bsmunconv: INFO: moving aside /etc/security/audit_startup.
bsmunconv: INFO: restore /etc/rc3.d/S81volmgt.
bsmunconv: INFO: removing c2audit:audit_load from /etc/system.
bsmunconv: INFO: stopping the cron daemon.
The Basic Security Module has been disabled.
Reboot this system now to come up without BSM.
Notice that the script should be run at single user or run level 1 because it makes system changes. It also
restores the volume management facility. The system needs to be rebooted to complete the operation.
Device Management
BSM contains a feature that protects devices attached to the system. It does the following:
¾ Stops multiple users from accessing a device simultaneously
¾ Stops anyone else from reading the data you might have just written to a device
¾ Stops anyone else from overwriting your data on a device
¾ Prohibits anyone else from getting information or data from a device after you have used it
Device management maintains some files to achieve this:
¾ /etc/security/device_allocate – A file that contains access control information about each device
¾ /etc/security/device_maps – Associates physical devices with logical file names
¾ /etc/security/dev – A directory containing all the relevant device files and used for locking
There are also some commands associated with BSM device management:
¾ allocate – Used to allocate a specific device to a user