control: tags -1 +moreinfo Dear Eric,
Thanks for your report! On Thu, May 28, 2020 at 5:21 PM Eric Marsden <[email protected]> wrote: > > I can confirm this bug. > It's unclear to me why this is necessary, but changing the line > ExecStart=/usr/bin/stubby > to > ExecStart=/usr/bin/stubby -C /etc/stubby/stubby.yml > in /lib/systemd/system/stubby.service fixes the problem. I'm confused because, * on the one side, debian CI test can confirm the regression you reported: https://ci.debian.net/packages/g/getdns/unstable/amd64/ * on the other side, I cannot confirm this issue on my sid box: # dpkg -i libgetdns10_1.5.2-1_amd64.deb stubby_1.5.2-1_amd64.deb # service stubby restart # service stubby status May 28 22:27:17 SID systemd[1]: Started DNS Privacy Stub Resolver. May 28 22:27:17 SID stubby[2145]: [13:27:17.172842] STUBBY: Read config from file /etc/stubby/stubby.yml May 28 22:27:17 SID stubby[2145]: [13:27:17.174068] STUBBY: DNSSEC Validation is OFF May 28 22:27:17 SID stubby[2145]: [13:27:17.174290] STUBBY: Transport list is: May 28 22:27:17 SID stubby[2145]: [13:27:17.174426] STUBBY: - TLS May 28 22:27:17 SID stubby[2145]: [13:27:17.174551] STUBBY: Privacy Usage Profile is Strict (Authentication required) May 28 22:27:17 SID stubby[2145]: [13:27:17.174672] STUBBY: (NOTE a Strict Profile only applies when TLS is the ONLY transport!!) May 28 22:27:17 SID stubby[2145]: [13:27:17.174793] STUBBY: Starting DAEMON.... Anyway, I'll try to upload the workaround with "-C /etc/stubby/stubby.yml" hardcoded in service file. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
