https://bugzilla.redhat.com/show_bug.cgi?id=2217335
Bug ID: 2217335
Summary: dnscrypt-proxy auto-enables itself after installation
Product: Fedora
Version: rawhide
OS: Linux
Status: NEW
Component: dnscrypt-proxy
Severity: medium
Assignee: davide(a)cavalca.name
Reporter: pemensik(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
go-sig(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
I have installed dnscrypt-proxy to look into its documentation. I were using
unbound+dnssec-trigger and wanted it to continue. But after a reboot my
configuration were broken and VPN redirection did not work. I have found that
happened because dnscrypt-proxy has a custom way to auto-enable itself on
installation. I do not think this is allowed by packaging guidelines.
Reproducible: Always
Steps to Reproduce:
1. dnf install unbound dnssec-trigger
2. dnf enable --now dnssec-triggerd
3. dnf install dnscrypt-proxy
4. reboot
Actual Results:
my explicitly configured unbound has failed to startup, because there is
different service listening on the same port already. I have never chosen to
replace that by dnscrypt-proxy.
Expected Results:
The service is enabled only manually, by usual configuration via systemctl:
systemctl enable --now dnscrypt-proxy
Fedora allows auto-enabled services only when they do not modify other
services. That does not happen directly, but by listening on common domain port
on 127.0.0.1 it effectively does. If it used alternative localhost address it
might be okay. But it must not as it is now.
This service has not a FESCo ticket required to be enabled by default:
https://src.fedoraproject.org/rpms/fedora-release/blob/rawhide/f/90-defau...
I do not think it passes guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices...
It also does not use systemd macros, which I think it should use:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_sy...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2217335
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...