samba - Apr 2004 - %20Re:%20samba%203.0%20vfs%20module%20problem

Hi Mariusz,

I found this thread at SAMBA.ORG:

snip...

 I can't remember for certain, but try using a relative
path.
> (e.g. vscan-mksd.so).
I tried relative and non-relative path, with this same effect 
but you've right because in manual for samba-vscan we can read 
that in samba 3.0 we should use relative path.
I had increase debug level of samba daemon and in my log I 
have found
[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
*******************************************************
after that, I had type:
cd /usr/local/samba/lib/vfs
ln -s vscan-mksd.so vscan-mksd.so.so
and now I see in log from my workstation:
[2003/12/12 07:41:34, 3] smbd/vfs.c:vfs_init_default(201)
   Initialising default vfs hooks
[2003/12/12 07:41:34, 3] smbd/vfs.c:vfs_init_custom(227)
   Initialising custom vfs hooks from [vscan-mksd.so]
[2003/12/12 07:41:34, 5] lib/module.c:smb_probe_module(102)
   Probing module 'vscan-mksd.so'
[2003/12/12 07:41:34, 5] lib/module.c:smb_probe_module(113)
**********************************************************
   Probing module 'vscan-mksd.so': Trying to load from 
/usr/local/samba/lib/vfs/v
scan-mksd.so.so
**********************************************************
[2003/12/12 07:41:34, 5] smbd/vfs.c:smb_register_vfs(191)
   Successfully added vfs backend 'vscan-mksd'
[2003/12/12 07:41:34, 5] mks/vscan-mksd.c:init_module(510)
   samba-vscan (vscan-mksd 0.3.4) registered (Samba 3.0), (c) 
by Rainer Link, Ope
nAntiVirus.org
[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
[2003/12/12 07:41:34, 0] smbd/vfs.c:vfs_init_custom(254)
   Can't find a vfs module [vscan-mksd.so]
[2003/12/12 07:41:34, 0] smbd/vfs.c:smbd_vfs_init(317)
   smbd_vfs_init: vfs_init_custom failed for vscan-mksd.so
but it's still not-working, and I don't know why, tomorrow I 
will try do symlink to the other places where samba can search 
this modules, now my company is working and I can do any test.
If anyone have any sugestion I will gracefull
regards

Mariusz

..snip

Could you solve this problem meanwhile?
I'm fighting with same problem.
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.
What did you do?

Thank's for help!

With best regards

Rainer Breuer

WERKZEUGPROFI
Mockel + Breuer oHG
Heuweg 20
06886 Lutherstadt Wittenberg
T.: +49 (0) 34 91 / 64 64 64
F.: +49 (0) 34 91 / 64 64 - 999
M.: RBreuer@WERKZEUGPROFI.de

Hallo@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