Till, many thanks for the info! Now it seems Ubuntu and Suse are in sync regarding the defaults for user access which is certainly very good when the end-user experience of different distros is very similar.
I like to learn which tool Ubunto uses to implement the "desktop-user" access. We use resmgr, see http://forge.novell.com/modules/xfmod/project/?resmgr and its HAL add-on hal-resmgr which are both free software under "GPL v2 or later". Another comment regarding the "scanner" group in general: Because of the many all-in-one devices I think a separate "scanner" group doesn't make sense to have it by default. In openSUSE I use udev rules files for SANE and for HPLIP which put all scanner and all HPLIP device files simply only into the "lp" group because I think this is a reasonable default. In our sane-backends package I modify the generated tools/udev/libsane.rules file as follows: All GROUP="scanner" are replaced by GROUP="lp". The reasons are: There is no group "scanner" in /etc/group for openSUSE. For all-in-one devices (e.g. "EPSON Stylus" devices) the group must be "lp" so that the CUPS usb backend which runs as user "lp" (who is member of the group "lp") can send printing data to the printer unit (i.e. the printer interface of the USB device). It is sufficiently secure and reasonable easy to use by default the same group "lp" for printers and scanners because both kind of devices usually require physical user access (to get the printed paper or to place a paper on the scanner) so that both kind of devices should usually require the same kind of security. Note that for hal-resmgr the wording is currently opposite: For hal-resmgr I simply use the HAL capability "scanner" in our HAL fdi files for all scanners and all HPLIP devices (i.e. even for plain HP printers) to grant r/w access also for HP printers. For the future I think about to have the capability "lp" also in HAL/hal-resmgr to get a consistent wording. -- needs a proper daemon or cupsys integration https://bugs.launchpad.net/bugs/149045 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
