This is an archive of past FreeBSD releases; it's part of the FreeBSD Documentation Archive.
During the development stage, a few users reported problems with normal configuration. Some of these problems are listed below:
multilabel flag does not stay
enabled on my root (
It seems that one out of every fifty users has this problem, indeed, we had this problem during our initial configuration. Further observation of this so called "bug" has lead me to believe that it is a result of either incorrect documentation or misinterpretation of the documentation. Regardless of why it happened, the following steps may be taken to resolve it:
/etc/fstab and set the root
ro for read-only.
Reboot into single user mode.
Reboot the system into normal mode.
/ and change the
and reboot the system again.
Double-check the output from the
mount to ensure that
multilabel has been properly set on the
root file system.
After establishing a secure environment with MAC, I am no longer able to start X!
This could be caused by the MAC
partition policy or by a mislabeling in
one of the MAC labeling policies. To
debug, try the following:
Check the error message; if the user is in the
insecure class, the
partition policy may be the culprit.
Try setting the user's class back to the
default class and rebuild the database
cap_mkdb command. If this
does not alleviate the problem, go to step two.
Double-check the label policies. Ensure that the
policies are set correctly for the user in question, the
X11 application, and
If neither of these resolve the problem, send the error message and a description of your environment to the TrustedBSD discussion lists located at the TrustedBSD website or to the Ogólna lista dyskusyjna FreeBSD mailing list.
When I attempt to switch from the
to another user in the system, the error message
_secure_path: unable to state .login_conf.
This message is usually shown when the user has a higher
label setting then that of the user whom they are attempting to
become. For instance a user on the system,
joe, has a default label of
who has a label of
biba/high, cannot view
joe's home directory. This will happen
root has used the
su command to become
or not. In this scenario, the Biba integrity model will not
root to view objects set at a lower
In normal or even single user mode, the
root is not recognized. The
whoami command returns 0 (zero) and
su returns who are you?.
What could be going on?
This can happen if a labeling policy has been disabled,
either by a sysctl(8) or the policy module was unloaded.
If the policy is being disabled or has been temporarily
disabled, then the login capabilities database needs to be
reconfigured with the
label option being
removed. Double check the
file to ensure that all
label options have
been removed and rebuild the database with the
This may also happen if a policy restricts access to the
master.passwd file or database. Usually
caused by an administrator altering the file under a label
which conflicts with the general policy being used by the
system. In these cases, the user information would be read
by the system and access would be blocked as the file has
inherited the new label. Disable the policy via a
sysctl(8) and everything should return to normal.
All FreeBSD documents are available for download at https://download.freebsd.org/ftp/doc/
Questions that are not answered by the
documentation may be
sent to <freebsd-questions@FreeBSD.org>.
Send questions about this document to <freebsd-doc@FreeBSD.org>.