HP-UX Bastille Version B.3.3.01 Release Notes

4 Known issues and workarounds
4.1 Changes made by HP-UX Bastille might cause other software to stop
working
To revert the system to the state it was in before you ran HP-UX Bastille:
# bastille -r
4.2 Cannot use X because $DISPLAY is not set
The user requests the X interface, but the $DISPLAY environment variable is not set. Set the
environment variable to the desired display to correct the problem.
4.3 System is in original state
The user attempts to revert changes with the -r option, but there are no changes to revert.
4.4 HP-UX Bastille must be run as root
HP-UX Bastille must be run as the root user because the changes it makes affect system files.
4.5 Problems opening, copying, or reading files
Error messages citing problems performing these operations are usually related to NFS file systems
that do not trust the root user on the local machine. Consult the options section in the fstab manpage
for details.
4.6 Errors related to individual configuration files
Errors about individual configuration files indicate:
• That a system is too heavily modified for HP-UX Bastille to make effective changes.
• That the files, locations, or permissions of the HP-UX Bastille installation directories have been
changed.
4.7 HP Secure Shell locks you out of your system immediately when
passwords expire
You might need PAM patch: PHCO_24839 (HP-UX 11.11) available at the HP IT Resource Center:
https://www2.itrc.hp.com/service/patch/mainPage.do
4.8 HP-UX Bastille configures a firewall using IPFilter
The most common conflicts are with firewalls. When a network service that HP-UX Bastille did not
turn off explicitly is not working, verify the firewall rules pass the ports needed. For more information,
see ipfstat(8) and ipmon(8).
4.9 Security Patch Check
Security Patch Check is being deprecated in favor of SWA.
4.1 Changes made by HP-UX Bastille might cause other software to stop working 9