Bug#798625: systemd-networkd: Runs arbitrary inappropriate scripts on network changes

[Josh Triplett]

On Wed, Sep 30, 2015 at 01:34:47PM +0200, Martin Pitt wrote:
> Control: tag -1 pending
> 
> Hello all,

Hi Martin,

> as discussed, I reverted the if-*.d/ calling in git now. I replaced it
> with a focussed (although admittedly a bit hackish) helper unit to
> update resolvconf from networkd for now, and this will be completely
> inert if you don't use resolvconf.
> 
> If you don't want this in Debian either, I'm also happy with keeping
> this in the Ubuntu branch only.

I really appreciate your careful consideration on this issue, and for
reverting the general hook mechanism.

In my opinion, a special-case hook for resolvconf does not have the same
issues as a general hook mechanism.  It doesn't create an expectation of
future support or compatibility; it could be changed at will in future
versions if resolvconf or networkd becomes more capable (or if we switch
to systemd-resolved).  So, personally, I don't see the harm in keeping
this hook for networkd in Debian.  (I don't in any way speak for the
Debian systemd maintainers, though.)

I'd also be happy to help work on solutions for other software.  I still
owe you a response to your previous mail, as well.

- Josh Triplett