libsepol update #3559
Merged
libsepol update #3559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
**Summary** - `sepol_polcap_getnum`/`name()` are now exported as part of the shared libsepol interface - `sepol/policydb/flask.h` was removed - Removed restrictions in libsepol and checkpolicy that required all declared initial SIDs to be assigned a context - libsepol implemented a new, more space-efficient form of storing filename transitions in the binary policy and reduced the size of the binary policy - sepolgen sorts extended rules like normal ones - libsepol and libsemanage dropped old and deprecated symbols and functions - libsepol version was bumped to libsepol.so.2 - Add `monitoring.yml` - Add homepage - Fix license Part of #3554 **Packager note** While newer versions than 3.3 are available, our `libselinux` is only at 3.3, so I opted to use the same version here. Updating that sounds like a can of worms that I don't want to open. Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
**Summary** - Add `monitoring.yml` - Add missing builddep Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
TraceyC77
reviewed
Aug 17, 2024
There was a problem hiding this comment.
Looks good here. The packages build and install.
@ReillyBrogan and/or @silkeh , did you want to take a look?
|
Should be fine to merge this and see what breaks, I think. I've made #3618 as a follow-up. |
|
TBH we don't use selinux so I don't really see how updating the libselinux library would cause problems. It pretty much only exists in the repo because it's a build/run dep of other packages, and I can't imagine they use it beyond "is selinux enabled? no? then skip that part of the code". |
davidjharder
approved these changes
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
While newer versions than 3.3 are available, our
libselinuxis only at 3.3, so I opted to use the same version here. Updating that sounds like a can of worms that I don't want to open.Part of #3554
Test Plan
Updated using the two packages, rebooted, ran
sudo, saw that my system did not explode. Since we don't actually use SELinux in the kernel, I'm not sure how else exactly to test this.Checklist