I did another test and chmod u+s /usr/lib/cups/daemon/cups-lpd does allow one to print from a client running a rfc compliant lpr command I.e., a client that insists on connecting to a lpd server on reserved port below 1024 (we have one). I setup cups-lpd to be listening on my ubuntu box via inetd and tcp wrappers and it works.
Back to the Original Subject of this Bug Report ============================ To address the problem of having an ubuntu client printing to an RFC compliant lpd server I have succeeded in doing this by doing chmod u+s /usr/lib/cups/backend-available/lpd, i.e., what did not work with earlier now works! Perhaps an update did it or did you guys do something? So I have some requests: ================ Could you folks add a question(s) to debconf for this package that would allow people to turn setuid user bits on cups-lpd and the lpd backend (available) . By default it should not be on when the package installs but having the option to turn it on would solve the problem. Furthermore you could include some notes in the debconf warning people appropriately. And a README.Ubuntu.gz file. -- dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root https://launchpad.net/bugs/47773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
