Bug#843191: systemd-sysv-install: policy creds not carried forward

[Michael Biebl]

On Thu, 22 Dec 2016 14:54:22 +0100 Michael Biebl <biebl at debian.org> wrote:
> Am 04.11.2016 um 20:27 schrieb Felipe Sateler:
> > systemd-sysv-install is executed at the client side, not on the server
> > side. This is something that probably makes sense fixing upstream, as
> > units enabled/disabled via the bus are not synchronized with sysv
> > state.
> 
> Hm, a cheap workaround could be, to run update-rc.d using pkexec if
> uid!=0. This would require a second polkit prompt, but this would be
> better then failing with a permission denied.

So, Lennart seems to be not too enthusiastic to add support for running
systemd-sysv-install on the server side.

Should we add a simple $(id -u) != 0 to systemd-sysv-install then?
And what should we do in that case:
a/ exit 0 with a log message telling the user that update-rc.d could not
be run due to missing priviliges?
b/ use pkexec (if available) to run update-rc.d? As said, this would
result in 4 polkit prompts, which is not too pretty.




[1] https://github.com/systemd/systemd/issues/4957#issuecomment-268908786
-- 
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...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170103/07cfa7f6/attachment.sig>