[Pkg-cups-devel] Bug#614713: Re-open: cups-pdf: installation asks for a password

[Didier 'OdyX' Raboud]

Control: tags -1 +unreproducible 

Le lundi, 20 octobre 2014, 15.15:36 Martin-Éric Racine a écrit :
> > lpadmin has several ways of "gaining" authentication against a cups
> > daemon. The ones involved are
> > 
> > 1) "certificates" issued by the cups daemon (NOT to be confused with
> > SSL certificates, more to the point they should have been named
> > s.th. like "authentication tokens") [2], [3].
> > Whenever a client tries to talk to cupsd on localhost, it tries to
> > use the certificate data read from /var/run/cups/certs/<PID> or
> > ...certs/0 (certs directory owned by lp:lpadmin, mode 511) and
> > passes them to cupsd for authentication.
> > 
> > 
> > In case of installing cups-pdf within a chroot, said certs directory
> > just doesn't exist, so lpadmin has to resort to asking the user for
> > a password.
> 
> Thanks for this in-depth analysis.
> 
> As far as I can tell, this essentially makes CUPS itself
> non-installable inside a chroot. Makes one wonder what got into
> upstream CUPS authors to migrate to an architecture that requires a
> running daemon to work.

I cannot confirm this: CUPS 1.7 is installable and working inside a 
chroot, as long as the 631 port is available. Is this a bug with CUPS 
1.4 only? Has it been reproduced with later versions ?

Also, the cups-pdf logs in piuparts are fine: 
https://piuparts.debian.org/sid/source/c/cups-pdf.html

Cheers, OdyX

P.S. The current CUPS maintainers' mailing list is debian-printing at l.d.o
-- 
OdyX