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

nsjail requires listing it's own syscalls #38

Open
gtristan opened this issue Apr 26, 2024 · 0 comments
Open

nsjail requires listing it's own syscalls #38

gtristan opened this issue Apr 26, 2024 · 0 comments

Comments

@gtristan
Copy link

Currently I find myself needing to define a base policy for any executables I run:

//
// Kafel policy to allow nsjail a few syscalls to launch the executable.
//
POLICY NsJail {
    ALLOW {
        execve,
        prctl,
        prlimit64
    }
}

Otherwise I am getting audit messages like this:

type=SECCOMP msg=audit(1714125050.685:56): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=12366 comm="nsjail" exe="/usr/bin/nsjail" sig=31 arch=c000003e syscall=59 compat=0 ip=0x7f6dcd26b55b code=0x0AUID="unset" UID="root" GID="root" ARCH=x86_64 SYSCALL=execve

It seems to me that intuitively, nsjail should not apply the seccomp rules to itself, but only to the child, sandboxed process.

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

No branches or pull requests

1 participant