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

dist: harden systemd service unit #276

Merged
merged 1 commit into from
Jul 7, 2022

Commits on Jun 14, 2022

  1. dist: harden systemd service unit

    With this patch the systemd service will now run in a hardened sandbox
    that limits the kinds of subsystems available to the unit. This improves
    the overall security of the system, as nextcloud-spreed-signaling
    becomes almost pointless to exploit.
    
    The most notable changes include:
    
    - The entire fie system is mounted read-only with ProtectSystem=strict
    - No binaries are executable, apart from /usr/bin/signaling, with
      NoExecPaths=/ and ExecPaths=/usr/bin/signaling
    - The service cannot see any user on the system apart from the one that
      is running the process, with PrivateUsers=yes
    - Most of the /proc subsystem is inaccessible, and things like system
      stats may be unavailabe, with ProcSubset=pid
    - All home directories are inaccessible, with ProtectHome=yes
    - The kinds of permitted system calls are limited, via SystemCallFilter=
    
    I highly recommend you to read the systemd.exec(5) manual page to fully
    understand what these options do and how they can protect the system.
    https://www.freedesktop.org/software/systemd/man/systemd.exec.html
    Tachi107 committed Jun 14, 2022
    Configuration menu
    Copy the full SHA
    15a9bea View commit details
    Browse the repository at this point in the history