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

Restrict rest-server.service SystemCallFilter (disallow @resources and @privileged) #249

Closed

Conversation

eriksjolund
Copy link
Contributor

What is the purpose of this change? What does it change?

Add more systemcalls that should not be allowed to the SystemCallFilter= in rest-server.service.

Was the change discussed in an issue or in the forum before?

Yes, in the forum

https://forum.restic.net/t/adjust-systemcallfilter-in-rest-server-service-add-resources-and-privileged/6454/4

Checklist

  • I have enabled maintainer edits for this PR
  • I have added tests for all changes in this PR
  • I have added documentation for the changes (in the manual)
  • There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
  • I have run gofmt on the code in all commits
  • All commit messages are formatted in the same style as the other commits in the repo
  • I'm done, this Pull Request is ready for review

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
@@ -57,6 +57,8 @@ RestrictRealtime=true
# if your service crashes with "code=killed, status=31/SYS", you probably tried to run linux_i386 (32bit) binary on a amd64 host
SystemCallArchitectures=native
SystemCallFilter=@system-service
SystemCallFilter=~@resources
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me ~@resources leads to a crash on startup due to golang/go#46279 .

@MichaelEischer
Copy link
Member

Closing as the PR caused a crash during my tests.

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.

None yet

2 participants