refpolicy
wayland-keylogger
refpolicy | wayland-keylogger | |
---|---|---|
7 | 30 | |
281 | 151 | |
0.4% | - | |
9.3 | 0.0 | |
4 days ago | over 1 year ago | |
Python | C | |
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
wayland-keylogger
-
"Replacing" window manager in Wayland Session?
Intercepting inputs meant for other apps is easy and it's already been done via LD_PRELOAD.
-
What are the good reasons nowadays that someone still uses X instead of Wayland when their hardware supports Wayland? [...] if you're not an Nvidia user, I fail to see why you are still on X.
And all of this just for supposedly better "security", that can easily circumvented with trivial attacks.
-
X11 or Wayland?
Not in the same sense that there's a keylogger included with Windows, no. It's that it's easier to do on Xorg as opposed to Wayland. This isn't to say that it's impossible, however.
- dwm is great otherwise
-
What are the compromises of running on xorg insetead of wayland?
You can have keylogger on Wayland also without root priviledge. It's trivial: https://github.com/Aishou/wayland-keylogger
-
Detecting the use of “curl – bash” server side
> you can still deliver different experiences at runtime — but you’re not likely to have the superuser privileges needed to run a leylogger or read ~/.ssh/id_rsa, etc, at that point.
Keyloggers are trivial to do in userspace Linux via LD_PRELOAD attacks[0], and typically your user account has permission to read ~/.ssh/id_rsa.
[0] https://github.com/Aishou/wayland-keylogger
- KDE Wayland Tearing Protocol Ready to Be Merged
- I keylogger su linux necessitano il super user?
- Wayland or Xorg in 2022?
-
Has anyone used Landlock (new kernel stuff) for sandboxing? What do you use for sandboxing?
I have read that bare Linux is totally insecure (https://github.com/Aishou/wayland-keylogger) unless you use some means of sandboxing. That's why I have been reading a lot about firejail, AppArmor, Tomoyo, etc.
What are some alternatives?
selinux-policy-arch - SELinux policy with Arch Linux specific changes. Based on the refrence policy
dunst - Lightweight and customizable notification daemon
dind - Docker in Docker
opensnitch - OpenSnitch is a GNU/Linux interactive application firewall inspired by Little Snitch.
discovery-engine - Discover least permissive security posture, Network Microsegmentation, and Application behaviour based on visibility/observability data emitted from policy engines..
xdg-desktop-portal-wlr - xdg-desktop-portal backend for wlroots
cascade - A high level language for SELinux policy
keynav - retire your mouse.
tiny-snitch - an interactive firewall for inbound and outbound connections
qubes-issues - The Qubes OS Project issue tracker
sysbox - An open-source, next-generation "runc" that empowers rootless containers to run workloads such as Systemd, Docker, Kubernetes, just like VMs.
gamescope - SteamOS session compositing window manager [Moved to: https://github.com/ValveSoftware/gamescope]