refpolicy
discovery-engine
| refpolicy | discovery-engine | |
|---|---|---|
| 7 | 2 | |
| 281 | 28 | |
| 0.4% | - | |
| 9.3 | 7.6 | |
| 4 days ago | 7 months ago | |
| Python | Go | |
| GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
refpolicy
-
SELinux policies for Alpine Linux
Distributions often start with the SELinux reference policy rather than starting from scratch.
-
SELinux is unmanageable; just turn it off if it gets in your way
really? I don't mean understand how to apply a new label. I mean understand what the policies are and how they work, be able to create new ones that apply to you, and verify that the ones given to you by the distro are correct for your use. You're saying this is not hard to understand: https://github.com/SELinuxProject/refpolicy/blob/master/poli... ?
Otherwise you are blindly applying some black box.
-
Which SELinux policy should you use?
selinux-refpolicy-src pulls from the original SELinux Project refpolicy repo and just install-src these, which just places all policies into appropriate directory and does nothing futher, i. e. doesn't compile them to make usable
-
Need help writing rules, please
https://github.com/SELinuxProject/refpolicy/blob/4412ad507c5880d9ff52fd376c23183cc9ae10b7/policy/support/misc_patterns.spt#L55
-
Wayland Keylogger (2021)
Of those distributions, only Fedora sets SELinux to enforcing by default. Moreover, AFAIK Fedora (+ RHEL and Android) are the only distributions that had wide testing of the reference policy [1] [2]. So, if you enable SELinux with the reference policy on the other distributions that you mention, it is likely that you will run into all kinds of issues.
[1] https://github.com/SELinuxProject/refpolicy
[2] https://github.com/fedora-selinux/selinux-policy
-
Switching from CentOS/RHEL to openSUSE as main enterprise OS, experiencies and general tips?
No default or reference policy is provided in openSUSE Leap. SELinux will not operate without a policy, so you must build and install one. The SELinux Reference Policy Project (https://github.com/SELinuxProject/refpolicy/wiki) should be helpful in providing examples and detailed information on creating your own policies, and this chapter also provides guidance on managing your SELinux policy.
-
Is this legit? SELinux is preventing login from getattr access on the filesystem /dev/shm.
Interesting. I don't have a red hat based system handy at the moment to compare since I'm on holiday. Maybe that's just how they set up shm? If you compare to Reference Policy, it appears that the getattr permission you asked about is granted there: https://github.com/SELinuxProject/refpolicy/blob/8a1bc98a31a9f2396f3c1389f43ffb10df31157f/policy/modules/system/systemd.te#L600
discovery-engine
-
SELinux is unmanageable; just turn it off if it gets in your way
KubeArmor (https://github.com/kubearmor) makes implementing SELinux policies easy for your host / k8s workloads.
Please do checkout the project and provide your valuable feedback.
All of our policies for SElinux are Auto generated using https://github.com/accuknox/discovery-engine
Writing policies by hand is nearly impossible, error prone and that is the exact problem we are trying to solve - to make SELinux and AppArmor easy for K8s workloads and now host based workloads.
-
KubeArmor adds support for SELinux
Auto Policy discovery for KubeArmor: https://github.com/accuknox/auto-policy-discovery
What are some alternatives?
wayland-keylogger - Proof-of-concept Wayland keylogger
cascade - A high level language for SELinux policy
selinux-policy-arch - SELinux policy with Arch Linux specific changes. Based on the refrence policy
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
dind - Docker in Docker
libdropprivs - Example code (will be library) for dropping privileges
tiny-snitch - an interactive firewall for inbound and outbound connections
firejail - Linux namespaces and seccomp-bpf sandbox
sysbox - An open-source, next-generation "runc" that empowers rootless containers to run workloads such as Systemd, Docker, Kubernetes, just like VMs.