Bug#747073: [cups-daemon] Doesn't work with systemd
Le samedi, 25 octobre 2014, 00.46:15 Josh Triplett a écrit :
> On Sat, Oct 25, 2014 at 09:11:38AM +0200, Didier 'OdyX' Raboud wrote:
> > For the record; given my (current) understanding of the problem, I
> > agree with CUPS upstream choices here: refusing to support v4mapped
> > IPv6 sockets while supporting IPv4 sockets is a sane choice, which
> > systemd ought to support.
>
> While I agree that systemd needs to cover this case, why do you think
> CUPS shouldn't support v4mapped?
>
> Did you read the document I previously linked to about not using
> v4mapped *on the wire* but using it *within a system*?
Let's rephrase then: my current position is that I will follow
upstream's choices in socket management; I don't have enough resources
myself to change how CUPS works in this regard.
That said, part of the problem is that CUPS does "localhost" matching to
verify that the incoming connections are allowed by its own
configuration. In a large scheme of things, CUPS-when-run-on-a-systemd-
system could probably "blindly" trust systemd sockets and not second-
judge whether they are legit or not; the responsibility to decide on
which addresses CUPS should be triggered would be entirely deferred to
systemd. But that's not how CUPS works currently. :-)
Cheers,
OdyX
Reply to: