Saned denies access

ferrari · 03-10-2018, 04:57 PM

BTW, I note that the Ubuntu guide you referred to mentioned using the following config directives in the saned.socket unit file

Code:

# Defaults for the saned initscript, from sane-utils

# To enable under systemd please read README.Debian
# Set to yes to start saned under SysV
RUN=no

# Set to the user saned should run as
RUN_AS_USER=saned

I don't use that (and it's not mentioned in 'man saned' either), so my /etc/systemd/system/saned.socket looks like this

Code:

[Unit]
Description=saned incoming socket

[Socket]
ListenStream=6566
Accept=yes
MaxConnections=1

[Install]
WantedBy=sockets.target

ferrari · 03-10-2018, 05:03 PM

Quote:

Thank you so much for trying to solve this. The 'funny' thing is that I also made it work some time ago on my older PC, and it worked immediately with no issues...

There is a chance that this relates to the particular sane-backends version (sane-backends 1.0.26git) in use on your system I guess. Are you able to upgrade the host perhaps?

burkina76 · 03-11-2018, 04:14 AM

I changed saned.socket by removing the first lines, now it's exactly the same as yours, but still no luck.
I also updated the host to 1.0.27 via github, nothing changes.
It's very interesting that you get the same behaviour I have using StandardInput=null. I'm using StandardInput=socket, as you do, but it may be that, for some reasons, this option is not set, and the issue is due to that...

ferrari · 03-11-2018, 04:58 AM

What happens if you remove (or comment out) the User= and Group= directives?

burkina76 · 03-11-2018, 05:48 AM

Nothing...

ferrari · 03-11-2018, 06:07 AM

Does /etc/default/saned exist? If so, what does it contain?

burkina76 · 03-11-2018, 06:34 AM

Well, I don't know what happens, but now it works...
Looking at the log, now the correct IP appears asking access, and the access is granted. I can use the scanner from the client.
The only thing that occurs to me is that I didn't perform a reboot after the upgrade to 1.0.27. After the reboot, now it seems to work, it may be thanks to the update. At least, this seems to me the only possibility.
I will test it in the next few days, and let you know if it stops working again.
Thanks a lot for the help, I was completely stuck...

ferrari · 03-11-2018, 02:23 PM

Glad to have walked with you on this one, and good to read of you success with this finally!