Red Hat Bugzilla – Bug 487975
sane-backends doesn't ship with an xinetd conf
Last modified: 2016-10-07 12:16:59 EDT
Created attachment 333668 [details]
xinetd conf for saned
Description of problem:
sane-backends doesn't ship with an xinetd conf. One must be written to allow network scanning.
Version-Release number of selected component (if applicable):
Dropping the attached file in /etc/xinetd.d and enabling the service is enough.
Could this file be added to the package, please ?
Have you tested this with SELinux enabled?
BTW: sorry for not responding earlier, I kinda missed it when you first reported it...
No, I did not test this with SE Linux. Do you want me to try ? I'm not very SE Linux proficient, so I can do a basic test and simply report whether it works or not, but it'd took me some time to write the SE Linux rule if needed.
No pb about the delay to answer, I understand it's sometime hard to cope with the mail/bugzilla load.
If you currently have set SELinux to permissive mode, please check it out, it would be very helpful to me to know if it works (are you still on F-10 BTW?). If you have it switched off SELinux, you needn't bother because your filesystem is likely not labeled correctly (and relabeling takes quite some time).
SELinux is disabled, I'll switch it to permissive, so it'll get activated at next reboot (I need to switch kernel anyway). And yes, I'm still on F-10.
Shouldn't the bug status be changed to ASSIGNED ?
(In reply to comment #6)
> Shouldn't the bug status be changed to ASSIGNED ?
ok, I enabled SELinux in permissive mode. There are some avc denied messages, but none from sane.
Thanks, could you repeat that in enforcing mode (and restart xinetd to be sure after that)? Permissive mode isn't really conclusive to say that it works properly... I'll try it here on F-11 meanwhile.
I'm bit reluctant to go to enforcing as this machine is a multi-purpose home-server, and according to the logs, going to enforcing will break a lot of stuff... I guess you'll have to rely on your own testing, sorry about that :-(
It works here running as root, but I'd like to avoid this requirement. I'll submit an allocation request for a "saned" user and group, then I need to ensure that this user gets access to the scanner device files, mode and SELinux-wise.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This still applies to F11 and F12. Please bump version to block the annoying auto-closer.
This bug still apply to F12.
According to https://bugzilla.redhat.com/show_bug.cgi?id=520634 the saned user was created. Is there anything else blocking this ? (except -ENOTIME indeed :-)
Nils, any update ?
Need to test this somewhere with a scanner.
Hi Nils, did you had time to give this a try ? I can provide feedback if you point me at a scratch build or something. Thanks in advance.
(In reply to comment #17)
> Need to test this somewhere with a scanner.
I'm happy to test too, if you're still interested in this.
Totally dropped the ball on this, sorry.
I'll close this as a duplicate of bug #1091566 which deals with this using systemd rather than xinetd.
*** This bug has been marked as a duplicate of bug 1091566 ***