oasisprotocol / oasisprotocol/oasis-core

Tighten worker SECCOMP policy

Open
#1,203 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

c:runtime/loader c:security p:1
Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Description

We introduced a simple SECCOMP policy in #1188 which we can likely tighten further to reduce the attack surface.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #1188 and locating the worker's current SECCOMP policy in the Go code. Review the existing allowed system calls and worker behavior, then verify that the policy can be narrowed without breaking the worker; the issue is done when the reduced policy is implemented and its behavior is tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
operating-systems, security
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.