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

Initial implementation of a sandbox for OpenBSD #545

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

WickedShell
Copy link

Leverages pledge and unveil, and leaves a public API for other systems to follow. The API was designed to match the OpenBSD side pretty closely as that's the initial target, if a BPF/capsicum implementation is brought forward it may be worth changing the API, and we should be okay with that. (Neither of those targets are on my current list of things to actively implement).

I've been using this locally for a bit on an OpenBSD system, can confirmed that a Linux build still works fine on a quick test. I've invoked transcoding, the only major feature I haven't touched that I'm tracking is jukebox, which I'm not really sure how it's supposed to be working yet. I also was unsure how to invoke the database upgrade path that I can ensure works.

This is the first time I've done anything with Go, so any criticisms are welcome.

@WickedShell WickedShell force-pushed the sandbox-openbsd branch 2 times, most recently from 79abe3c to df763bd Compare November 19, 2024 17:02
Leverages pledge and unveil, and leaves a public API for other
systems to follow. The API was designed to match the OpenBSD side
as that's the initial target, if a BPF/capsicum implementation is
brought forward it may be worth changing the API, and we should be
okay with that.
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

Successfully merging this pull request may close these issues.

1 participant