Public bug reported:
>From the upstream patch:
"
If a boolean is encountered in a require block before the place where it is
declared it currently gets created with the state set to false no matter what
the declared state was. This only affects booleans in modules where the boolean
was also required in another module.
"
Basically, if a boolean was being set in a module other than 'base',
then it was not being honored and instead the default value was used.
For instance in the init policy the boolean init_upstart was set to
TRUE, but when the policy was installed the boolean was FALSE (as per
the default).
Description: Ubuntu Jaunty (development branch)
Release: 9.04
libsepol1 2.0.30-2
** Affects: libsepol (Ubuntu)
Importance: Undecided
Status: New
--
fix boolean state smashing
https://bugs.launchpad.net/bugs/344959
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
