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.

Sign up for GitHub

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

Jump to bottom

Make seccomp an optional feature #36

Open
slhmy opened this issue Jun 24, 2022 · 0 comments
Open

Make seccomp an optional feature #36

slhmy opened this issue Jun 24, 2022 · 0 comments
Assignees
@slhmy @akamya997
Labels
good first issue Good for newcomers hard May stay for a long time for solution high priority Urgent issue which needs to be fixed

Comments

@slhmy
Copy link
Member

slhmy commented Jun 24, 2022 •
edited
Loading

For a more flexible use(EX. we only want to monitor the rusage of the program, this can be used in MacOS which doesn't include libseccomp), libseccomp may not be included.

Also considering making judger just being the runner | dispatcher of the judge in the throw away container, in this case seccomp will be nearly useless and user group and namespace will be more necessary.
@slhmy slhmy added the good first issue Good for newcomers label Jun 24, 2022
@slhmy slhmy added hard May stay for a long time for solution low priority Don't need to fix immediately labels Jun 10, 2023
@slhmy slhmy added high priority Urgent issue which needs to be fixed and removed low priority Don't need to fix immediately labels Sep 12, 2023
@slhmy slhmy mentioned this issue Sep 12, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@slhmy slhmy

@akamya997 akamya997

Labels
good first issue Good for newcomers hard May stay for a long time for solution high priority Urgent issue which needs to be fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@slhmy @akamya997