Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add signals to AppArmorProfile spec #2755

Open
Edan-Hamilton opened this issue Mar 4, 2025 · 0 comments
Open

Add signals to AppArmorProfile spec #2755

Edan-Hamilton opened this issue Mar 4, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Edan-Hamilton
Copy link

What would you like to be added:

Add the ability to restrict signals with AppArmorProfiles. Should include read, write, send, or receive. Should be able to apply to specific signals, or all signals. Should be able to limit to a specific peer.

Why is this needed:

Signals allow communication between processes, which is an inherent security risk. Certain signals are commonly required, but most are not. Often a profile can be further restricted by allowing signals only to itself, or only to other processes with a specific profile.

@Edan-Hamilton Edan-Hamilton added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant