3c63da7cf8
When `services.resolved.enable` is set to true, the file /etc/resolv.conf becomes a symlink to /etc/static/resolv.conf, which is a symlink to /run/systemd/resolve/stub-resolv.conf. Without this commit, tor does not have access to this file thanks to systemd confinement. This results in the following warning when tor starts: ``` [warn] Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory [warn] Could not read your DNS config from '/etc/resolv.conf' - please investigate your DNS configuration. This is possibly a problem. Meanwhile, falling back to local DNS at 127.0.0.1. ``` To fix this, simply allow read-only access to the file when resolved is in use. According to https://github.com/NixOS/nixpkgs/pull/161818#discussion_r824820462, the symlink may also point to /run/systemd/resolve/resolv.conf, so allow that as well. |
||
---|---|---|
.. | ||
vaultwarden | ||
aesmd.nix | ||
certmgr.nix | ||
cfssl.nix | ||
clamav.nix | ||
fail2ban.nix | ||
fprintd.nix | ||
haka.nix | ||
haveged.nix | ||
hockeypuck.nix | ||
hologram-agent.nix | ||
hologram-server.nix | ||
munge.nix | ||
nginx-sso.nix | ||
oauth2_proxy.nix | ||
oauth2_proxy_nginx.nix | ||
opensnitch.nix | ||
physlock.nix | ||
privacyidea.nix | ||
shibboleth-sp.nix | ||
sks.nix | ||
sshguard.nix | ||
step-ca.nix | ||
tor.nix | ||
torify.nix | ||
torsocks.nix | ||
usbguard.nix | ||
vault.nix | ||
yubikey-agent.nix |