e17d4b05a1
It's very surprising that services.tor.client.enable would set services.privoxy.enable. This violates the principle of least astonishment, because it's Privoxy that can integrate with Tor, rather than the other way around. So this patch moves the Privoxy Tor integration to the Privoxy module, and it also disables it by default. This change is documented in the release notes. Reported-by: V <v@anomalous.eu> |
||
---|---|---|
.. | ||
bitwarden_rs | ||
certmgr.nix | ||
cfssl.nix | ||
clamav.nix | ||
fail2ban.nix | ||
fprintd.nix | ||
fprot.nix | ||
haka.nix | ||
haveged.nix | ||
hologram-agent.nix | ||
hologram-server.nix | ||
munge.nix | ||
nginx-sso.nix | ||
oauth2_proxy_nginx.nix | ||
oauth2_proxy.nix | ||
physlock.nix | ||
privacyidea.nix | ||
shibboleth-sp.nix | ||
sks.nix | ||
sshguard.nix | ||
tor.nix | ||
torify.nix | ||
torsocks.nix | ||
usbguard.nix | ||
vault.nix | ||
yubikey-agent.nix |