[Samba] Re: Re: samba 3.0 vfs module problem

[Rainer Link]

Hallo at WERKZEUGPROFI.de wrote:
> [2003/12/12 06:38:00, 3] smbd/vfs.c:vfs_init_custom(227)
>    Initialising custom vfs hooks from [vscan-mksd.so]
> [2003/12/12 06:38:00, 5] lib/module.c:smb_probe_module(102)
>    Probing module 'vscan-mksd.so'
> [2003/12/12 06:38:00, 5] lib/module.c:smb_probe_module(113)
> *******************************************************
>    Probing module 'vscan-mksd.so': Trying to load from 
> /usr/local/samba/lib/vfs/vscan-mksd.so.so
                                       ^^^^^^
> *******************************************************


> [2003/12/12 07:41:34, 2] lib/module.c:do_smb_load_module(64)
>    Module '/usr/local/samba/lib/vfs/vscan-mksd.so.so' loaded
						^^^^^^

> Could you solve this problem meanwhile?
> I'm fighting with same problem.

For Samba 3.x the correct setting is simply
	vfs objects = vscan-mksd

No ".so" extension, no path at all. See man 5 smb.conf for details.

> With the help of your thread, i'm able to load the vscan-clamav module, but it seems to me, that the scanner doesn't work. If i copy the EICAR test to the share, there is no warning or anything else.

samba-vscan logs everything via syslog, so check /var/log/messages. 
Moreover, please read through the INSTALL file of samba-vscan, here's a 
quote of the upcoming 0.3.5 release (support of libclamav is not
available in earlier releases, so please just skip it):

- Clam AntiVirus
   samba-vscan (clamav module) can be configured to use for the
   Clam AntiVirus daemon (clamd) or the ClamAV library (libclamav).
   Usage of clamd is default.

   Daemon:
   You need Clam AntiVirus Daemon from http://www.clamav.net/. As socket 
name
   /var/run/clamd is assumed. You can modify this via CLAMD_SOCKET_NAME
   in vscan-clamav.h or via clamd socket name = <string> in the run-time
   configuration file.
   The socket must have read/write permissions for everyone (i.e.
   chmod a+rw /var/run/clamd), as smbd runs under various user IDs (i.e.
   "nobody" or as the user "xyz", when user "xyz" is connected to his home
   directory). This could be a security risk, as now an attacker could pass
   arbitrary commands to Clam AntiVirus Daemon, so we need a better
   solution here ...

   libclamav:
   To use the ClamAV library instead, use the --with-clamav-lib switch for
   ./configure. Keep in mind, if vscan-clamav is build and linked for
   libclamav, you must rebuild the module if you decide to use clamd
   instead.


HTH

best regards,
Rainer Link