Am 10.06.2015 um 11:37 schrieb Michael Biebl:
> Am 09.06.2015 um 13:14 schrieb Marc Haber:
>> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote:
>>> This change is imho too invasive for being backported to the stable v215
>>> in jessie. The first Debian version carrying that fix is 217-
Am 09.06.2015 um 13:14 schrieb Marc Haber:
> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote:
>> This change is imho too invasive for being backported to the stable v215
>> in jessie. The first Debian version carrying that fix is 217-1, so I'm
>> closing it for this version.
>
> How
On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote:
> This change is imho too invasive for being backported to the stable v215
> in jessie. The first Debian version carrying that fix is 217-1, so I'm
> closing it for this version.
How about shipping a /etc/systemd/resolved.conf with a n
On Fri, Jun 05, 2015 at 09:45:28PM +0200, Michael Biebl wrote:
> Am 04.06.2015 um 16:02 schrieb Marc Haber:
> > The documentation in resolved.conf(5) suggests that the compiled-in
> > list does only apply if there is no other definition of DNS-Servers.
> > This is not the case here, and the fact th
Control: tags -1 + fixed-upstream confirmed
Control: fixed -1 220-1
Am 05.06.2015 um 21:45 schrieb Michael Biebl:
> Hi
>
> Am 04.06.2015 um 16:02 schrieb Marc Haber:
>> The documentation in resolved.conf(5) suggests that the compiled-in
>> list does only apply if there is no other definition of D
Hi
Am 04.06.2015 um 16:02 schrieb Marc Haber:
> The documentation in resolved.conf(5) suggests that the compiled-in
> list does only apply if there is no other definition of DNS-Servers.
> This is not the case here, and the fact that systemd-resolved takes
> the definition from /etc/systemd/networ
Am 05.06.2015 um 17:49 schrieb Marc Haber:
> On Thu, Jun 04, 2015 at 06:05:04PM +0200, Christoph Anton Mitterer wrote:
>> Anyway, can we merge the issues?
>
> Objected. #787731 is a real bug. Just mentioning that the default is a
> bad default does not make it the same issue. The issue here ist th
On Thu, Jun 04, 2015 at 06:05:04PM +0200, Christoph Anton Mitterer wrote:
> Anyway, can we merge the issues?
Objected. #787731 is a real bug. Just mentioning that the default is a
bad default does not make it the same issue. The issue here ist that a
default is used while the local admin did what
On Thu, 2015-06-04 at 16:52 +0200, Marco d'Itri wrote:
> > Having google's resolvers in the first place poses a potential data
> > leak.
> This was discussed to death in #761658.
With basically all affected parties having said that this is a very bad
idea, security-wise, privacy-wise and in terms
On Jun 04, Marc Haber wrote:
> The documentation in resolved.conf(5) suggests that the compiled-in
> list does only apply if there is no other definition of DNS-Servers.
> This is not the case here, and the fact that systemd-resolved takes
> the definition from /etc/systemd/network/int181.network
Package: systemd
Version: 215-17
Severity: normal
On all systems I checked, there is a file /etc/systemd/resolved.conf
with the following contents:
[19/516]mh@barrida:~$ cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or m
11 matches
Mail list logo
