Bug#923081: privacy invasion due to automatic fallback to Cloudflare
biebl at debian.org
Wed Feb 27 15:29:24 GMT 2019
On Mon, 25 Feb 2019 14:29:42 +0000 Toni Mueller <toni at debian.org> wrote:
> reopen 923081
> Hi Andreas,
> On Mon, Feb 25, 2019 at 09:25:48AM +0100, Andreas Henriksson wrote:
> > (Not sure why you think Cloudflare is a problem but Google is not, but
> > oh well.....)
> well, I think you are misreading my bug report.
> I definitely think that *both* are a problem, but until I took a closer
> look, I was just unaware of this entire thing. And, btw, I would prefer
> to use something that has sane defaults and can be used without
> attending a special "systemd university" first - I just have different
> priorities than that.
> > If *you* enable systemd-resolved (which is shipped completely disabled)
> > then *you* are expected to know how to configure it.
> I don't know how you can conclude that *I* enabled it. In fact, it is
> enabled by default as far as I can see, because there is only one way to
> disable it, which is setting "DNSStubListener" to "no", while the
> default is "yes", as also indicated by this snippet from the config file
> as shipped in this file: systemd_240-6_amd64.deb:
> Please see also the appropriate section about this option on this web
> Please don't claim that this service is disabled as shipped in Debian
> when it is not.
Andreas is correct.
systemd-resolved is *not* enabled by default in Debian.
$ systemctl is-enabled systemd-resolved
If that reports a different state for you, then you have enabled the
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers