libsane and acl group selection in udev rules

[Martin Owens]

On Wed, 2011-10-26 at 18:32 +0200, Julien BLACHE wrote:
> saned exists, it should not be used to share scanners over the network
> because sharing scanners is a bad idea that exposes every user of said
> scanners to data leak by just forgetting a sensitive document inside
> the
> scanner. Also, image data is transmitted unencrypted on the network.
> 
We have a successful shared scanner at a community center, people are
scanning in photos of their kids. There is a sign to take your documents
when finished scanning, it's in the same room as the computers. No
security problems, it's a public space.

Why break libsane so I don't accidentally implement something that is a
bad idea? Remember, sharks with freekin' lazers! We might not approve of
the use, but it's not good to force people to edit udev rules in
undocumented ways to do something that the system can still do.

Perhaps some added documentation in the udev rules or a commented out
section that people can enable when they need to 'do the wrong thing'?
You could even stick in some of your points directly into the file to
make sure people understand it's wrong.

Seconded on the problems with sane, but we deal with what we have at the
moment and that's saned.

Martin,