On Mon 30 Apr 2018 at 16:18:01 +0300, Abdullah Ramazanoglu wrote: > On Mon, 30 Apr 2018 14:24:19 +0200 to...@tuxteam.de said: > > On Mon, Apr 30, 2018 at 03:00:07PM +0300, Abdullah Ramazanoglu wrote: > > > On Mon, 30 Apr 2018 06:43:03 +0200 to...@tuxteam.de said: > > > > [...] > > > > > > It seems this issue is fixed upstream. Would you like to check that? > > > > > > > > Tone down. Apply Hanlon's razor generously [...] > > > > > This is not about systemd or some bug or something. This is about > > > attitude. > > > > Exactly my point :-) > > Good one! :) :) > > > On a more practical note: care to double-check whether the > > issue is actually fixed upstream? > > AFAIK it is still there untouched in git sources, as originally mentioned in > the bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896806 > > That aside, the question of whether it will ever get fixed in upstream or not, > is of secondary importance. OTOH, the fact that official Debian developers and > maintainers adopted a stance of neglecting users' privacy is of utmost > importance.
systemd-resolved is not used and enabled by default. If a concerned user changes that situation, it is not exactly hard to alter the fallback DNS server(s). > I had taken Debian Social Contract and DFSG for granted for a long time. This > thing forced me to review my assumptions about Debian. Questioning one's assumptions from time to time is never a bad thing. -- Brian.
