>> >> in which case you have to be careful not to run into endless
>> >> recursion when trying to determine the list of available >>
>> devices... ;-)
Andy> Yes. Simple solution : Do not allow to re-export
Andy> netsaned-mounted scanners.
>> > Hmmh, you make the assumption it's easy for the net-proxy to determine
>> > whether it's re-exporting a device or not. I don't think it's that
>> > easy.
Andy> Well ... I assumed everything which has a driver-name starting with
Andy> net-should be left out ... This could be dynamically added to the
Andy> basename when exporting.
OK, I thought some more about it. Maybe the proper solution is to
view this as an authorization question. We change sane_get_devices()
and sane_open() to accept a pointer to an authorization structure. As
part of that authorization structure, we can keep info on whether this
is a local user or a remote user (e.g., a NULL authorization pointer
would imply local user as defined by getuid() etc). The net backend
(metanet) can then decide what to do with a get_device() request based
on the authorization: if it's a local user, return remote devices,
otherwise, return an empty list.
--david
--- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@azstarnet.com