Skip to content

Conversation

@aplanas
Copy link
Contributor

@aplanas aplanas commented Mar 15, 2023

Add a SELinux extended IMA policy as an example, and some documentation about how to use and extend it.

@aplanas
Copy link
Contributor Author

aplanas commented Mar 15, 2023

This IMA policy is using the SELinux types available in openSUSE, but this is the same one that is used in Fedora. Both are instances of the SELinux reference policy, so the types referenced on it are quite generic.

@aplanas aplanas force-pushed the fix_ima-policy branch 2 times, most recently from 8c92297 to 6b2d07c Compare March 17, 2023 08:05
@THS-on
Copy link
Member

THS-on commented Mar 17, 2023

We also have some IMA policies here: https://github.com/keylime/keylime/tree/master/demo/ima-policies

Maybe we should unify them in one place and then point the documentation to it.

@aplanas
Copy link
Contributor Author

aplanas commented Mar 17, 2023

Maybe we should unify them in one place and then point the documentation to it.

From a brief comparison, seems that the overlayfs fs ID was missing, and I added it now.

@codecov
Copy link

codecov bot commented Jul 6, 2023

Codecov Report

Merging #536 (9553c56) into master (636c80a) will increase coverage by 0.14%.
The diff coverage is 100.00%.

Additional details and impacted files
Flag Coverage Δ
e2e-testsuite 59.65% <100.00%> (+0.17%) ⬆️
upstream-unit-tests 59.92% <0.00%> (-0.14%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
keylime-agent/src/main.rs 37.04% <100.00%> (+1.23%) ⬆️

... and 1 file with indirect coverage changes

Add a SELinux extended IMA policy as an example, and some documentation
about how to use and extend it.

Signed-off-by: Alberto Planas <aplanas@suse.com>
@ansasaki ansasaki merged commit 381faac into keylime:master Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants