Git Product home page Git Product logo

Comments (6)

giuseppe avatar giuseppe commented on August 28, 2024 1

Can crun ignore seccomp entries for unknown syscalls?

wouldn't that be a potential security issue if the syscall is blocked?

And if we skip syscalls that are allowed, then the container can fail despite a correct configuration.

Are you using a static build for crun? Perhaps we could build seccomp from git master there

from crun.

giuseppe avatar giuseppe commented on August 28, 2024

that is a libseccomp issue: seccomp/libseccomp#177

There is not a release yet that includes that syscalls, but the version from master works fine

For Fedora, we are working on backporting these patches to libseccomp

from crun.

AkihiroSuda avatar AkihiroSuda commented on August 28, 2024

Can crun ignore seccomp entries for unknown syscalls?

from crun.

giuseppe avatar giuseppe commented on August 28, 2024

I've opened a PR for using seccomp from master: #158

from crun.

justincormack avatar justincormack commented on August 28, 2024

I think it is better to ignore unknown syscalls, otherwise it requires exactly synchronised updates of seccomp policies and libseccomp versions which is a huge burden on users. Many distros will not update libseccomp for new syscalls for kernels they are not shipping, so then you cannot change your seccomp policy at all, which makes default seccomp policies very difficult to implement at all. Almost all changes are new syscalls for new kernels, so people are rarely relying on them and will have fallbacks.

from crun.

giuseppe avatar giuseppe commented on August 28, 2024

I think it is better to ignore unknown syscalls, otherwise it requires exactly synchronised updates of seccomp policies and libseccomp versions which is a huge burden on users. Many distros will not update libseccomp for new syscalls for kernels they are not shipping, so then you cannot change your seccomp policy at all, which makes default seccomp policies very difficult to implement at all. Almost all changes are new syscalls for new kernels, so people are rarely relying on them and will have fallbacks.

thanks for the explanation. That makes sense to me. I've added a patch to a PR I was already working on (just to avoid rebases) and I've switched the default to not fail when an unknown syscall is found in the seccomp profile: #211

from crun.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.