Revert "seccomp: Block socketcall to prevent AF_ALG filter bypass"#23
Merged
Revert "seccomp: Block socketcall to prevent AF_ALG filter bypass"#23
Conversation
Blocking whole `socketcall` had much bigger impact on x86 binaries than anticipated. Drop the seccomp based block in favor of AppArmor/SELinux based one. Seccomp cannot filter socketcall(2) arguments because the address family is behind a userspace pointer that BPF cannot dereference. Only an LSM (AppArmor or SELinux) can deny AF_ALG via the security_socket_create hook in the socketcall path. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blocking whole
socketcallhad much bigger impact on x86 binaries than anticipated.Drop the seccomp based block in favor of AppArmor/SELinux based one (#22, moby/moby#52547)
Seccomp cannot filter socketcall(2) arguments because the address family is behind a userspace pointer that BPF cannot dereference.
Only an LSM (AppArmor or SELinux) can deny AF_ALG via the security_socket_create hook in the socketcall path.