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

Implementing libseccomp in PRoot #163

Closed
oxr463 opened this issue Feb 5, 2021 · 0 comments
Closed

Implementing libseccomp in PRoot #163

oxr463 opened this issue Feb 5, 2021 · 0 comments
Labels
Medium Sized Project Medium sized project is 175 hours

Comments

@oxr463
Copy link
Contributor

oxr463 commented Feb 5, 2021

Project Title: Implementing libseccomp in PRoot

Description:

PRoot contains it's own seccomp code for handling security permissions for running binaries. Instead of maintaining the legacy seccomp code, we would like to see libseccomp implemented. Below is a brief excerpt of the benefits this solution would provide:

We (libseccomp) will take care of cBPF creation, ABI issues,
and any syscall changes when a new kernel is released. Maintaining a custom
filter throughout all of that can be challenging.

This would also help with portability since libseccomp supports several different architectures.

Deliverable:

The current test suite should pass on recent Linux kernels with no failures, on all of the arches that PRoot supports.

Mentor: @oxr463

Skills: c, Linux, ptrace, syscalls, seccomp

Skill Level: Hard

Get started: See: proot-me/proot#106, proot-me/proot#195

@ddemaio ddemaio added the PRoot label Feb 8, 2021
@ddemaio ddemaio added PRoot and removed PRoot labels Feb 9, 2022
@ddemaio ddemaio added the Medium Sized Project Medium sized project is 175 hours label Feb 25, 2022
@ddemaio ddemaio removed the PRoot label Apr 25, 2022
@ddemaio ddemaio closed this as completed Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium Sized Project Medium sized project is 175 hours
Projects
None yet
Development

No branches or pull requests

2 participants