Consider a system that supports multiple users. When access to a resource, such as a scanner, should be limited to only some users, the classic solution is to create a "scanner" group and define users who should have scanner access as members of that group.
When a user changes to the scanner group in order to access the scanner, it would be a security fault if his images can be seen by other users in the scanner group. Therefore, when using the scanner, umask should be set by default to preclude access by other group members to new image files. If group access is desired, the user should explicitly arrange that - by change to the umask value during scanning, or to file attributes after scanning. SELinux provides more sophisticated access control, but is more work to maintain and therefore is less used when its capabilities are not required. The majority of Linux systems are single-user, or close to that, and scanner access control is not relevant, but this is no excuse to avoid security considerations. -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
