Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Felipe Sateler 2016-09-10 12:45: Control: forwarded -1 https://github.com/systemd/systemd/issues/4122 On 9 September 2016 at 19:36, Michael Biebl wrote: Am 10.09.2016 um 00:26 schrieb Michael Biebl: So, you'll also need to mask that name, i.e

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Oh, I guess I have an idea what's happening. systemd-resolve triggers the start via D-Bus activation. Yeah, that was my guess as well. Just seemed wrong to me given that the unit providing that service is masked. /usr/share/dbus-1/system-services/org.freedesktop.resolve1.service For

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Am 10.09.2016 um 17:45 schrieb Felipe Sateler: > Control: forwarded -1 https://github.com/systemd/systemd/issues/4122 > > On 9 September 2016 at 19:36, Michael Biebl wrote: >> Upstream's position on this is, that masks apply only on that particular >> name and not for any

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Control: forwarded -1 https://github.com/systemd/systemd/issues/4122 On 9 September 2016 at 19:36, Michael Biebl wrote: > Am 10.09.2016 um 00:26 schrieb Michael Biebl: >> So, you'll also need to mask that name, i.e >> dbus-org.freedesktop.resolve1.service > >

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Am 10.09.2016 um 00:26 schrieb Michael Biebl: > So, you'll also need to mask that name, i.e > dbus-org.freedesktop.resolve1.service https://github.com/systemd/systemd/issues/1873 is somewhat related. Upstream's position on this is, that masks apply only on that particular name and not for any

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Am 10.09.2016 um 00:20 schrieb Brian Kroth: > Michael Biebl 2016-09-09 23:33: >> Am 09.09.2016 um 22:47 schrieb Brian Kroth: >>> Package: systemd >>> Version: 230-7~bpo8+2 >>> Severity: normal >>> Tags: security >>> >>> Dear Maintainer, >>> >>> systemd appears to start

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Michael Biebl 2016-09-09 23:33: Am 09.09.2016 um 22:47 schrieb Brian Kroth: Package: systemd Version: 230-7~bpo8+2 Severity: normal Tags: security Dear Maintainer, systemd appears to start systemd-resolved, even when it's been masked, in the background even when an

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Am 09.09.2016 um 22:47 schrieb Brian Kroth: > Package: systemd > Version: 230-7~bpo8+2 > Severity: normal > Tags: security > > Dear Maintainer, > > systemd appears to start systemd-resolved, even when it's been masked, > in the background even when an unprivileged user calls systemd-resolve. >

Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked

Package: systemd Version: 230-7~bpo8+2 Severity: normal Tags: security Dear Maintainer, systemd appears to start systemd-resolved, even when it's been masked, in the background even when an unprivileged user calls systemd-resolve. However, calls to start the service manually via systemctl