Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

suggesting --security-opt seccomp:unconfined is irresponsible #220

Open
b-jam opened this issue Nov 17, 2021 · 1 comment
Open

suggesting --security-opt seccomp:unconfined is irresponsible #220

b-jam opened this issue Nov 17, 2021 · 1 comment

Comments

@b-jam
Copy link

b-jam commented Nov 17, 2021

Here it is recommended to disable docker seccomp in order to run athenapdf.

According to https://docs.docker.com/engine/security/seccomp/, name_to_handle_at syscall has a good reason to be blocked, that is - Cause of an old container breakout

Rather than suggest users to allow historic vulnerabilities, it makes sense to instead refactor not to use the name_to_handle_at syscall.
libudev is the culprit here, I'm not sure where that dependency is pulled in.

@cedws
Copy link

cedws commented Nov 27, 2021

Container escapes are a dime a dozen anyway. It should not be used as a blast door for running untrusted or insecure software.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants