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

Named Unix socket connect() control by path #36

Open
gnoack opened this issue Jun 14, 2024 · 0 comments
Open

Named Unix socket connect() control by path #36

gnoack opened this issue Jun 14, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@gnoack
Copy link

gnoack commented Jun 14, 2024

As remarked by @thejh in https://lore.kernel.org/linux-security-module/CAG48ez3NvVnonOqKH4oRwRqbSOLO0p9djBqgvxVwn6gtGQBPcw@mail.gmail.com/ -- establishing a connection to a named Unix Domain Socket is done through connect(2), passing the filename in the struct sockaddr, and that is not covered by Landlock's file system control. It would be nice if such connections could be restricted by file path, because the file path is how such services are identified.

(Remark, a much coarser control to forbid Unix Domain Socket connections will be possible with #6 once these patches are in, but that is by socket type, not by file path.)

@l0kod l0kod added the enhancement New feature or request label Jun 18, 2024
@l0kod l0kod added this to Landlock Jun 18, 2024
@l0kod l0kod moved this to Backlog in Landlock Jun 18, 2024
@l0kod l0kod added the good first issue Good for newcomers label Nov 13, 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 good first issue Good for newcomers
Projects
Status: Backlog
Development

No branches or pull requests

2 participants