[sane-devel] saned.conf hostname format

[Sebastien Sable]

Henning Meier-Geinitz <henning at meier-geinitz.de> writes:

> Yes. It happens if the server doesn't accept the client because it's
> not in saned.conf. I'm not sure, if this is the correct way, to reject
> the client, however...

Here is the log of inetd. It shows that saned is called with the full
adress of the host every time :

with incubus.snv.jussieu.fr in /etc/sane.d/saned.conf

Sep 21 15:09:48 inova saned[32103]: access by saned-user at incubus.snv.jussieu.fr accepted 
Sep 21 15:09:54 inova saned[32103]: exiting 

with incubus in /etc/sane.d/saned.conf

Sep 21 15:10:29 inova saned[32110]: access by saned-user at incubus.snv.jussieu.fr rejected 
Sep 21 15:10:29 inova saned[32110]: exiting

Between those two tests I have just changed the line in
/etc/sane.d/saned.conf.

Maybe saned compares the string `incubus.snv.jussieu.fr` with
`incubus` and decides that the host is not allowed.

[taking a quick look at saned source code....]
found saned.c and function check_host

it checks hosts.equiv (I have no such file) and saned.conf for
authorized hostnames = rhost

then compares with the hostname of the client = he->h_name

if (strcasecmp (rhost, he->h_name) == 0 || strcmp (rhost, "+") == 0)
    access_ok = 1;

So I suppose that is the problem if he->h_name is
incubus.snv.jussieu.fr and rhost is incubus.

Maybe when you tested on your side the client was in hosts.equiv or
the gethostbyaddr reports something different?

I could modify saned.c to log the different values if it is needed.

> Probably your server doesn't know the name of your client without its
> domain name? --> /etc/hosts or name server problem?

I am pretty sure the problem is not related to the network. The log
above shows that saned is launched and I use those 2 computers very
often together for many services :

sable at incubus:~$ ping inova
PING inova.snv.jussieu.fr (134.157.163.71): 56 data bytes
64 bytes from 134.157.163.71: icmp_seq=0 ttl=254 time=0.7 ms

--- inova.snv.jussieu.fr ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.7/0.7/0.7 ms
sable at incubus:~$ ssh inova
...
sable at inova:~$ ping incubus
PING incubus.snv.jussieu.fr (134.157.37.137): 56 data bytes
64 bytes from 134.157.37.137: icmp_seq=0 ttl=254 time=0.9 ms

--- incubus.snv.jussieu.fr ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.9/0.9/0.9 ms

bye

-- 
Sébastien Sablé <Sebastien.Sable at snv.jussieu.fr>
http://inova.snv.jussieu.fr/~sable/