Using Fedora 10, the kavmon.pl fails to build:

# ./kavmon.pl -b
=== Configure kernel module using kernel sources from /lib/modules/2.6.27.21-170.2.56.fc10.x86_64/build
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for linux kernel sources... /lib/modules/2.6.27.21-170.2.56.fc10.x86_64/build
checking for linux kernel version file... /lib/modules/2.6.27.21-170.2.56.fc10.x86_64/build/include/linux/utsrelease.h
checking for linux kernel version... 2.6
checking for changing of LSM interface... not changed
checking for linux/syscalls.h... yes
checking for module arch... 64
checking for sys_call_table... found, address 0xffffffff8133f640
checking for sys_call_table readonly... yes
checking for ia32_sys_call_table... found, address 0xffffffff81347a58
checking for ia32_sys_call_table readonly... yes
checking for security_ops... found, address 0xffffffff817cfe10
checking for register_security... found, address 0xffffffff8113cc46
checking for mod_reg_security... configure: error: "Cannot resolve symbol mod_reg_security"

Suggestions of how to resolve? Thank you!

It could be with the mod_reg_security module in that kernel you're using. Fedora 10 is not officially supported for KAV for Linux Fileserver. Please check, if mod_reg_security is compiled into your kernel or running as module.

In the linux kernel 2.6.24 LSM were converted into static modules, so there is no such API anymore.
I do not remember exactly in the meantime if they have already reverted it back by kernel version 2.6.27.
As far as I remember, even if they reverted it, they simply have broken compatibility with older API...

It seems that i'm actually having this problem. Is there any wokraround? a have slackware 12.2 with kernel 2.6.27.7.
I'd better consider a kernel upgrade than a downgrade.
Any way to use just the scanner manually without the kavmon module?

KAV for Linux FS 5.7 doesn't support kernels 2.6.27.x and higher. It will be enabled in 6th version (release is planned in September).

Kavmon is needed for real-time protection, you can use on-demand scan without it.

That's good news for the Kaspersky users. Due to this not working, we're moving customers and my team to a different product family for antivirus and security services. We would have liked to continue to use Kaspersky but require better service and product support for the Windows and Linux.

it's not news for Kaspersky users that have had an occasional chance to take a look at the applications' system requirements indeed...

what do you mean by better service and support wrt broken LSM in the newer Linux kernels?

We've worked with clients running more than one varient and version of Linux in their landscapes. Working with Kaspersky to support F10 for clients evaluating or more often deploying Fedora 10, it has not been an option due to support. It would be a good option for clients if Kaspersky was a good bit more aggressive in staying 'current' on the Linux scene - as customers evaluating and trying Linux distributions include platforms that are out of Kaspersky's current support scope (including F10). Thankfully there are options for clients who do run RHEL, Fedora, etc. other than Kaspersky to provide the security coverage they need.

Additionally, Kaspersky's support in resolving problems with the Business Space product - via phone support - (two specific issues, one on 64 bit Windows XP and one on 32 bit XP producing severe performance problems) have largely gone without useful response from Kaspersky. The age of the Business Space offering and the two significant instances of support problems has forced two environments to have us explore and produce a non-Kaspersky solution.

I'm disappointed that we've had to go elsewhere as I personally like Kaspersky but without:
- current Business Space product offering
- support response effectiveness
- an effective multi-distribution Linux offering

we are having to go elsewhere. I will bring customers back if these things can change from Kaspersky - but it'll be a while before the new contracts we've setup with customers and their antivirus/security vendor selection run out.

thanks for detailed explanation of your opinion,

as for support in resolving problems - it depends on your region and support lines you are connected with...

as for more responsive offerings for new linux distros - this should be one more point to note for our linux product marketing, agree...