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

Getting away from libseccomp #2724

Open
utam0k opened this issue Mar 6, 2024 · 5 comments
Open

Getting away from libseccomp #2724

utam0k opened this issue Mar 6, 2024 · 5 comments
Assignees

Comments

@utam0k
Copy link
Member

utam0k commented Mar 6, 2024

We will start looking into the possibility of implementing our own seccomp. libseccomp dependency issues have erupted in various places.
It would not be necessary to actually support that many architectures. However, we only need to know the number of the system call for each archs.

@utam0k utam0k self-assigned this Mar 6, 2024
@utam0k
Copy link
Member Author

utam0k commented Mar 6, 2024

I'll give it a try to implement PoC

@jprendes
Copy link
Contributor

jprendes commented Mar 6, 2024

That's great!
Particularly, as libseccomp is LGPL licensed.
I know runc adds the libseecomp tarbal to their release due to static builds (see here), something we don't currently do.

@YJDoc2
Copy link
Collaborator

YJDoc2 commented Mar 6, 2024

This would be great! Let me know if I can help in any way 💜

@YJDoc2
Copy link
Collaborator

YJDoc2 commented Apr 11, 2024

Hey, we should also take a look at https://github.com/rust-vmm/seccompiler

@utam0k
Copy link
Member Author

utam0k commented Apr 11, 2024

Hey, we should also take a look at https://github.com/rust-vmm/seccompiler

Thanks for sharing. I have already checked it but it doesn't support seccomp notify.

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

No branches or pull requests

3 participants