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

Restrict use of SYSV message queues #30

Open
gnoack opened this issue Apr 8, 2024 · 1 comment
Open

Restrict use of SYSV message queues #30

gnoack opened this issue Apr 8, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@gnoack
Copy link

gnoack commented Apr 8, 2024

System V message queues are acquired with msgget(2).
The key for acquiring these is in a system-global namespace,
so it seems that we might want to restrict their use somehow,
even when they are rarely used in practice today, judging by Debian code search.

There are existing LSM hooks for these, called security_msg_queue_*.

Capsicum is also restricting System V IPC (https://www.usenix.org/legacy/event/sec10/tech/full_papers/Watson.pdf, page 4)

@l0kod
Copy link
Member

l0kod commented Apr 11, 2024

Looks good! For IPCs, I think being able to scope them to Landlock domains would makes sense in most cases and be easy to use. I'm not sure it would be worth it to be able to create dedicated rules.

Anyway, that's really close to #7, #8, and #29.

@l0kod l0kod added the enhancement New feature or request label Apr 11, 2024
@l0kod l0kod added this to Landlock Apr 11, 2024
@l0kod l0kod moved this to Backlog in Landlock Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants