the problem with this is that doing the config as non-root would mean the backend would need elevated permissions in order to write its config out into /etc/...
if the user is willing to run the front-end the first time as root, and then the backend saves the config changes, that might be ok. otherwise the user will have to re-config under each user account. remember also that sane works on platforms that dont use unix account setups... allan On Fri, 25 Feb 2005, Johannes Meixner wrote: > > Hello, > > On Feb 24 20:06 Oliver Rauch wrote (shortened): >> May be we need an additional flag to the existing ADVANCED flag, may be >> a CONFIGURE flag. This way the backend would define what the user can >> select and we already would have a configuration tool: the frontend. >> The backend could save the last selected setting in its own >> configuration file as a default option (although this also could be done >> by the frontend). > > This would be great! > > Please have in mind that it must be possible to seperate configuring > from daily usage. > It would lead to chaos if many different (unexperienced) users > who may access the scanner for example via saned and net backend > can configure it as they like. > > In particular it should be possible to request admin authentication > for configuring. > As an example have a look how printer configuration is done in CUPS: > Via 'lppasswd' root can permit any user to act as a CUPS admin > and in cupsd.conf admin authentication can be disabled at all. > > > Kind Regards > Johannes Meixner > -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
