[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-09-18 Thread Martin Pitt
cupsys (1.2.3-1ubuntu2) edgy; urgency=low . * debian/patches/56_dirsvc.dpatch: Update patch so that a patch/unpatch cycle restores the source properly instead of breaking dirsvc.c in two different places. * debian/rules: Install 'lpd' backend suid root (root:lp 4754), so that

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-09-11 Thread Martin Pitt
The easy and correct fix for edgy is indeed to install the backend suid root and drop privileges right after opening the port. ** Changed in: cupsys (Ubuntu) Assignee: (unassigned) => Martin Pitt Status: Confirmed => In Progress -- dapper cupsys can not print to rfc compliant lpd ser

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-08-17 Thread Walter Tautz
Just to be clear printing from Ubuntu/Dapper to RFC compliant lpd server it suffice to chmod u+s /usr/lib/cups/backend-available/lpd. However having the ability to do chmod u+s /usr/lib/cups/daemon/cups-lpd is also convenient as it solves a slightly similar problem or should I say reverse issue. S

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-08-17 Thread Walter Tautz
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 inet

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-07-11 Thread Kurt Pfeifle
Oh, I forgot a very prominent and important service that does not comply with your principles for security, Ante: Samba. I just checked with the box of a friend who runs Dapper: it has the original Dapper packages of Samba, and all smbd and nmbd processes do run as root -- dapper cupsys can

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-07-11 Thread Kurt Pfeifle
Ante Karamatić wrote: 'Mike knows that RunAsUser and "helper functions for init scripts" (i.e. start-stop-daemon) are two totally different things.' I'm sure he knows that. What he meant to say was that a start-stop daemon solution should then also use a port above 1024 (instead of 63

[Bug 47773] Re: [Bug 47773] Re: [Bug 47773] Re: [Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-26 Thread Walter Tautz
Ante Karamatić wrote: > On Mon, 26 Jun 2006 15:04:28 - > Walter Tautz <[EMAIL PROTECTED]> wrote: > > >> We aren't going to bring back RunAsUser. All of the Linux distros >> already provide helper functions for their init scripts to run as >> a different user, I suggest you look there if you

[Bug 47773] Re: [Bug 47773] Re: [Bug 47773] Re: [Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-26 Thread Walter Tautz
Ante Karamatić wrote: > On Mon, 26 Jun 2006 15:04:28 - > Walter Tautz <[EMAIL PROTECTED]> wrote: > > >> We aren't going to bring back RunAsUser. All of the Linux distros >> already provide helper functions for their init scripts to run as >> a different user, I suggest you look there if you

[Bug 47773] Re: [Bug 47773] Re: [Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-26 Thread Ante Karamatić
On Mon, 26 Jun 2006 15:04:28 - Walter Tautz <[EMAIL PROTECTED]> wrote: > We aren't going to bring back RunAsUser. All of the Linux distros > already provide helper functions for their init scripts to run as > a different user, I suggest you look there if you really want to > cripple your CUPS

[Bug 47773] Re: [Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-26 Thread Walter Tautz
Ante Karamatić wrote: > It's between "Rejected" and "Confirmed". For fixing this bug we should > run cups as root or introduce setuid program. > > ** Changed in: cupsys (Ubuntu) >Status: Needs Info => Confirmed > > Hi, In a recent thread Michael Sweet outlined point by point why not runn

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Ante Karamatić
It's between "Rejected" and "Confirmed". For fixing this bug we should run cups as root or introduce setuid program. ** Changed in: cupsys (Ubuntu) Status: Needs Info => Confirmed -- dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root https://launchpad.net/b

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Kurt Pfeifle
So why is this bug still in status "needs info"? -- 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

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Ante Karamatić
Kurt thank you for clearing this up. As for Ubuntu patching source, you can very easily check it and you'll see Ubuntu has less than 100 lines of diff regarding to Debian package (if you exclude fixes from CUPS CVS). Most of those lines are in cupsd.conf, not the source. I think buglist is not for

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Kurt Pfeifle
_Like_ *this*? Or 'like' ''this''? '''Hmm...''' -- 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

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Kurt Pfeifle
How does this thingie work? No markup guide in sight... -- 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

[Bug 47773] Re: dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as root

2006-06-24 Thread Kurt Pfeifle
--> "You do not need/want cups to run as root for this." <-- Yes you do, at least in the context of this bug report. The bug report explicitely names an "RFC compliant LPD server". In case you are not familiar with RFC 1179 (which is the one that descibes LPD), please have a look