Permissions problem for sane

[Mehmet Erol Sanliturk]

On Sun, Aug 9, 2015 at 10:16 PM, Adrian Chadd <adrian.chadd at gmail.com>
wrote:

> Hi!
>
> Why isn't this the default behaviour for the saned package? Would it
> be possible to make it just be said default behaviour?
>
>
> -a
>
>
>

When KDE or Gnome is running , or whatever reason some of their facilities
are running during a GUI set up , permissions defined in OS level are
prevented for ordinary "user" level .

When "user" needs to use some facilities , permitted for the "root" and
"user" with respect to loader.conf , or rc.conf , or other *.conf files ,
also it is necessary to define them in PolicyKit or other *Kit
configuration files .

Mostly these files are implicitly "secret" because , there was a circular
referencing for them :
In Handbook , "see KDE/GNOME sites" , from KDE/GNOME sites  "see your OS
documentation"
without any visible information about them .

In Linux , OS and these parts are synchrony in distributions because *Kit
part are completing missing parts of OS .
In FreeBSD , these *Kit's are only preventing facilities alrady present in
OS .

This situation is making FreeBSD very hard to use .


Mehmet Erol Sanliturk



> On 6 August 2015 at 14:15, Warren Block <wblock at wonkity.com> wrote:
> > On Thu, 6 Aug 2015, Patrick Hess wrote:
> >
> >> Anthony Campbell wrote:
> >>>
> >>> Should I modify the permissions on /dev/ugen0.2?
> >>
> >>
> >> In contrast to what many other people might suggest, I'm personally not
> >> a big fan of providing users broad access to all kinds of device nodes.
> >> So instead of messing around with permissions, I prefer to make use of
> >> the saned(8) network daemon.
> >>
> >> This is actually pretty straightforward to set up. You'll need to add
> >> these two lines to your /etc/rc.conf:
> >>
> >>    saned_enable="YES"
> >>    saned_uid="root"
> >>
> >> Now either reboot the machine or run the following command to start
> >> the network daemon right away:
> >>
> >>    # service saned start
> >>
> >> Then add the following line to /usr/local/etc/sane.d/net.conf:
> >>
> >>    localhost
> >>
> >> Any non-privileged user should now be able to access the scanner.
> >> For starters, try to get a list of scanners available on the server:
> >>
> >>    > scanimage -L
> >>    device `net:localhost:plustek:libusb:/dev/usb:/dev/ugen1.2'
> >>    is a Canon CanoScan N1240U/LiDE30 flatbed scanner
> >>
> >> The nice part about using saned(8) is that you can easily make the
> >> scanner available to other machines on the network. Just add your
> >> network to the server's /usr/local/etc/sane.d/saned.conf and then
> >> add an entry for the server to the /usr/local/etc/sane.d/net.conf
> >> on each of the clients.
> >
> >
> > This is the kind of stuff we should be adding to the Handbook section on
> > scanners.  Thank you for posting it!
> >
> > _______________________________________________
> > freebsd-questions at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>