On Tue, Jan 08, 2013 at 07:14:26AM +0100, Christian PERRIER wrote: > Quoting jswmb01x (jswmb01x@mobistarmail.be): > > Clarification : > > Adding "user1" to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is "forbidden"), not for printing. > Hmmm, well, then I would say this is cups that changed its behaviour > and made it a requirement to have privleges in order to add a printer, > even "plug n' play" toys. Which makes sense to me. Indeed, even on > Windows, unprivileged users cannot add local printers to the system > (but most Windows users don't notice as they always virtually work as > "root" on their machines). > > That makes it less of a requirement to have the first created user in > lpadmin, after more thinking. > > This bug could then even be "wontfix". I don't understand your reasoning. We also add the user to sudo if no root password is set. And to netdev for the administration of network devices. Along the same lines the user should be added to lpadmin. What annoys me more is that it seems to be inflationary to add new default groups, like debian-tor. I've got nothing against TOR, but filesystems like NFSv3 are limited to 16 groups to be transmitted with a request. If a user has more groups, the others are dropped. Hence we should be somewhat careful how many different groups we introduce, especially by default. |: Kind regards Philipp Kern
Attachment:
signature.asc
Description: Digital signature