[Pkg-cups-devel] Bug#640939: Moreinfo

[Wolfgang Schweer]

Hi all,

during BSP Essen I stumbled upon this thread, now I found time for 
some testing.

[Martin Pitt]
>I discussed this with Till, and we both have no real idea how to get
>to a situation where lpadmin as root asks for a password. It is
>already called with -h /var/run/cups/cups.sock to ensure it's not
>talking to a remote server. It seems you need a particular cups
>configuration to achieve this.

-------------------------------------------------------------------------

cups 1.5.3-2.6, system without Kerberos, DefaultAuthType set to 
"Negotiate" just for testing, no other changes to cupsd.conf:
 
root at eagle:~# lpadmin -h /var/run/cups/cups.sock -d <valid printer name>
Password for root on localhost?
[need to press return key]
lpadmin: Unauthorized
root at eagle:~# lpadmin -h 127.0.0.1 -d <valid printer name>
lpadmin: Unauthorized
root at eagle:~# lpadmin -h localhost -d <valid printer name>
lpadmin: Unauthorized

root at eagle:~# 

-------------------------------------------------------------------------

IMO the root pw questioning was most probably introduced by adding 
extended Kerberos support upstream, therefore expecting a valid 
hostname/IP as server argument causing problems in related cases, too.

(upstream revision 9732 on trunk, see URL in message #54 above.)

Maybe replacing "-h /var/run/cups/cups.sock" by "-h localhost" would 
solve the reported problem (and related ones) -- if no sideeffects 
are triggered.

A related problem on a kerberized system: #663995, 
upstream: http://www.cups.org/str.php?L4140


Regards,

Wolfgang

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cups-devel/attachments/20121127/9339f65c/attachment.pgp>