mirror of
https://github.com/openwrt/packages.git
synced 2025-12-22 01:44:32 +04:00
754a9908f4
Run AdGuard Home without superuser privileges, by granting the binary capabilities through ujail. AdGuard Home writes new config files, so it must have r/w access to the directory where these files live. Which means existing configs must be migrated to a new directory, /etc/adguardhome, by default. CAP_NET_BIND_SERVICE and CAP_NET_RAW capabilities are based on the official documentation linked below. Link: https://github.com/AdguardTeam/AdGuardHome/wiki/Getting-Started#running-without-superuser-linux-only Signed-off-by: George Sapkin <george@sapk.in>
13 lines
509 B
Plaintext
13 lines
509 B
Plaintext
config adguardhome 'config'
|
|
# All paths except for PID must be readable by the configured user
|
|
option config '/etc/adguardhome/adguardhome.yaml'
|
|
# Where to store persistent data by AdGuard Home
|
|
option workdir '/var/lib/adguardhome'
|
|
option pidfile '/run/adguardhome.pid'
|
|
option user 'adguardhome'
|
|
option group 'adguardhome'
|
|
option verbose '0'
|
|
# Files and directories that AdGuard Home has read-only access to
|
|
# list jail_mount '/etc/ssl/adguardhome.crt'
|
|
# list jail_mount '/etc/ssl/adguardhome.key'
|