[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#702227: Permission of the backend too strict for a backend chain (beh, jasmine)



On Sat, 9 Mar 2013 18:48:47 +0100 "Didier 'OdyX' Raboud" <odyx@debian.org> wrote:
> I can't disagree with that.
>
> As far as I can read that bug:
> i) running backends not as root will likely break some working behaviours;
> ii) apparently a non-standard backend, not even in Debian doesn't work in that
> situation.
>
> So, as I would rather not try to fix something not broken for most standard
> Debian uses, and as I haven't been convinced that fixing that is an
> improvement over the current situation, I'm hereby tagging this bug as
> wontfix.
>
> Cheers,
>
> OdyX
>
>


I would like to put in my opinion that this bug be fixed. Our system uses beh with lpd, with a string like:
beh:/1/0/15/lpd://192.168.0.101/LPT1?reserve=yes

Both beh and lpd are standard CUPS backends that come with Debian, so one would think they would work together, but with the default /usr/lib/cups/backend/beh permissions of 755, sending a job like this will just hang. I fix this on my system by giving /usr/lib/cups/backend/beh permissions of 700, but of course permissions can be obliterated during a package upgrade, so it would be good if this would be fixed. Thanks,

Nick


Reply to: