Topic: Recompile Kernel for eTrust anti-virus

[Jon Roberts]

I have been trying to install CA eTrust antivirus on the e-smith as it is the enterprise antivirus software we use.  I have succeeded in this and can run it as a scheduled job, however to install as a real-time checker, the eTrust installation needs to recompile the kernel.

I'm using 5.6 with current updates applied and have downloaded the kernel from http://mirror.contribs.org/smeserver/contribs/dmay/mitel/contrib/dev-tools/SME56/ and followed the related HowTo.  All went well.

The CA site claims their antivirus to be compatible with Red Hat Linux 6.2, 7.0, 7.1, 7.2 and 7.3.  So all would seem well.

However, when I try and install the software & OK the recompile, I just get the following error message:

This distribution is not supported

CA-ENF not supported on this release of OS.
Exiting...

SetupENF error 30
CAIENF does not support this version of the operating system

The CAIENF installation has failed -- error 30.

I've searched CA's site and the web generally, but can't find anything.  Anyone have any suggestions as to what I could try or am I just out of luck.

[Graeme Fleming]

.. it may be looking for the /etc/redhat-release (if memory serves me) file - standard with all Redhat systems but not required for SME.

Check out the file from someone with a standard Redhat install; get a copy and give it a whirl.

HTH

[Nathan Fowler]

I don't have SSH in front of me, but it may have something to do with /etc/redhat-release or something along those lines.

[Jon Roberts]

Thanks for the feedback.  I created the /etc/redhat-release file with a single record of "7.3" and it seems to do the trick.  Or at least it progressed to the compile.

I then came across another problem some time into the compile with the message:

"CAIENF-E-FAIL: make modules_install failed for Linux source. Please contact CA-Support"

I have contacted support and am waiting on a response (the one I expect being - Sorry but we don't support an e-smith install).  So I have another question.

I could set up a RedHat 7.3 server (which is supported) and install eTrust on that.  Assuming the kernel compile works in that case, can I just copy the new Kernel onto the e-smith?  If so, what files need to be copied?

Any tips / ideas gratefully recieved.

I have searched the forums, but can't find a response that tells me what I need.  However, if there is already a HowTo or some other source of info out there, just point me in that direction.

Thanks

[Nathan Fowler]

Do you have make installed and all the other compile libraries, not just the kernel headers/source?

[Jon Roberts]

Nathan Fowler wrote:
>
> Do you have make installed and all the other compile
> libraries, not just the kernel headers/source?

Nathan,

I think everything is installed.  I downloaded the source RPM & followed the HowTo.  Here is a log of what I did:

RPMs Files:

cpp-2.96-112.i386.rpm          kernel-headers-2.4.9-31.i386.rpm
gcc-2.96-112.i386.rpm          kernel-source-2.4.18-3.i386.rpm
glibc-devel-2.2.5-40.i386.rpm

# rpm -ivh *
Preparing...                ########################################### [100%]
   1:cpp                    ########################################### [ 20%]
   2:kernel-headers         ########################################### [ 40%]
   3:glibc-devel            ########################################### [ 60%]
   4:gcc                    ########################################### [ 80%]
   5:kernel-source          ########################################### [100%]

'To confirm Make was already installed I did:
#rpm -q make
make-3.79.1-8

In accordance with the HowTo, I then did:
# cd /usr/src/linux-2.4.18-3
# make
(taking defaults for all except for following:
Symmetric multi-processing support (CONFIG_SMP) [N/y/?] answer 'Y')
# make dep

which all seemed to work OK.  I'm not too worried about having to build a RedHat 7 machine and compiling on that if I thought that would solve the problem, but I need to know I could just copy the kernel back off the RedHat server onto the e-smith (& which files needed copying, of course).

Thanks for your help so far.

[Nathan Fowler]

Hmm, looks like you have everything you need.

I think you could copy the kernel off the machine, I've done it in the past.  Just make bzImage and copy the bootable image over, update lilo.conf, etc.

I'd also keep the kernel headers/source on hand on that SME box for the kernel you compiled on the RH box.

[Jon Roberts]

I have been advised by CA that for eTrust to work on RedHat 7.3 the kernel should be version 2.4.18-3.  The e-smith 5.6 uses version 2.4.18-5.

Now I can probably find and replace the kernel (given enough time) but - being more than a little cynical - I'm not convinced that this isn't just an easy get out for CA.

So:
(1) is it likely that the differences between these two version could cause the errors I have been getting and
(2) if there really are significant differences between the two versions, what's the chances that rolling back to the earlier one would break my e-smith install.

Thanks again for all the useful help & advice

[George]

Jon Roberts wrote:
 
> I have been advised by CA that for eTrust to work on RedHat
> 7.3 the kernel should be version 2.4.18-3.  The e-smith 5.6
> uses version 2.4.18-5.
>
> Now I can probably find and replace the kernel ...

No, you should change your vendor. Any vendor which *forces* you to use an old and insecure kernel should be avoided. (eTrust indeed!).

G.