-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Apr 29, 2018 at 06:53:08PM +0200, Martin Hanson wrote:
> I have posted this bug report
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806 that has been
> rejected by the maintainer.
>
> Maybe I have misunderstood the issue completely, but I do have some
> experience with legal issues and AFAIK, there IS a problem here.
>
> I am posting this to the mailing list in order to get "more eyes on the
> issue".
In a nutshell the above bug report states that systemd-resolved
has hard-coded fallbacks for Google DNS servers (8.8.8.{4,8})
(and BTW for Google NTP servers too). Those fallbacks will AFAIU
only become active if no other alternative exists, but then the
user might be led to (tacitly) accept terms of service (s)he doesn't
know about and possibly doesn't approve of.
Martin, you might have a point there.
Could Debian just replace those by something non-functional (e.g.
localhost)? DNS wouldn't be there if not configured, a behaviour
which has been OK before arrival of systemd-resolved?
Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlrl/8oACgkQBcgs9XrR2kbzOACfQFhtPinoUs028225dssUvvPH
dlQAnRJy/Fb3xfhBz6/n8FEAfp5Zjxza
=zv+T
-----END PGP SIGNATURE-----
