fix boolean state smashing
Bug #344959 reported by
Caleb Case
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libsepol (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
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
Revision history for this message
| Caleb Case (calebcase) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in libsepol: | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package libsepol - 2.0.30-2ubuntu1
---------------
libsepol (2.0.30-2ubuntu1) jaunty; urgency=low
* Boolean state was not being read correctly from modules resulting in an
invalid compiled policy (LP: #344959).
-- Caleb Case <email address hidden> Tue, 17 Mar 2009 16:50:58 -0400