Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ClamAV: users

Update Clamav

 

 

ClamAV users RSS feed   Index | Next | Previous | View Threaded


marco.draghi at qsolutionsgroup

Apr 29, 2004, 6:59 AM

Post #1 of 9 (681 views)
Permalink
Update Clamav

I've received the warning about the outdated version of my clamav-0.67 too.
For install the new clamav-0.70.tar.gz do I need to uninstall the first one
and after install the new one, or just install the last version over 0.67??

Thanks, Marco.


beddok2 at ch-cahors

Apr 29, 2004, 8:15 AM

Post #2 of 9 (652 views)
Permalink
Re: Update Clamav [In reply to]

Marco Draghi a écrit :

>I've received the warning about the outdated version of my clamav-0.67 too.
>For install the new clamav-0.70.tar.gz do I need to uninstall the first one
>and after install the new one, or just install the last version over 0.67??
>
>Thanks, Marco.
>
>
>

install over.

René


nhoughton at sourcefire

Jun 27, 2012, 11:29 AM

Post #3 of 9 (612 views)
Permalink
Re: update clamav [In reply to]

On Jun 27, 2012, at 8:12 AM, Matthew Olney wrote:

> Apparently, the answer to this is on the wiki, but it is having issues.
>
>> Begin forwarded message:
>>
>>> From: Ilyas Doskhozhayev <idoskhozhayev [at] gmail>
>>> Date: June 27, 2012, 5:45:28 AM EDT
>>> To: jesler [at] sourcefire
>>> Subject: update clamav
>>>
>>> Hi thank all you team for this antivirus tool/
>>>
>>> My question is on debian i have servers that can not update virus database directly from internet, so they update from local repository on network
>>> So can i make clamav update from my local repository on server that has internet ?
>>>
>>>
>>> I use this source list to update from repository on server
>>>
>>> deb http://10.0.1.11/localrepository /
>>>
>>> Thank in advanse

Here's the relevant information from the wiki:

Solution 1: Use an HTTP proxy

This solution is really easy to implement and is bandwidth efficient.

Install a proxy server (i.e. squid) and then tell your freshclam clients to use it. This can be done by setting the HTTPProxyServer parameter in freshclam.conf (see man 5 freshclam.conf for the details).

Solution 2: Serve .cvd files from a local web server

This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you.

Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files from http://database.clamav.net to the webserver’s DocumentRoot.

Add this line to freshclam.conf on machine1.mylan:

ScriptedUpdates off

First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on your clients so that it reads:

DatabaseMirror machine1.mylan

ScriptedUpdates off

--
Nigel Houghton
Head Mentalist, Time Lord
SF VRT Department of Intelligence Excellence
http://vrt-blog.snort.org/ && http://labs.snort.org/
Attachments: signature.asc (0.48 KB)


bruno.barosa at pessoaseprocessos

Jul 9, 2012, 2:08 AM

Post #4 of 9 (580 views)
Permalink
Re: update clamav [In reply to]

Hello again,

Good morning and a good week for all

anyone has got news on this issue?

Regards
Bruno

On 27-06-2012 19:29, Nigel Houghton wrote:
> On Jun 27, 2012, at 8:12 AM, Matthew Olney wrote:
>
>> Apparently, the answer to this is on the wiki, but it is having issues.
>>
>>> Begin forwarded message:
>>>
>>>> From: Ilyas Doskhozhayev<idoskhozhayev [at] gmail>
>>>> Date: June 27, 2012, 5:45:28 AM EDT
>>>> To: jesler [at] sourcefire
>>>> Subject: update clamav
>>>>
>>>> Hi thank all you team for this antivirus tool/
>>>>
>>>> My question is on debian i have servers that can not update virus database directly from internet, so they update from local repository on network
>>>> So can i make clamav update from my local repository on server that has internet ?
>>>>
>>>>
>>>> I use this source list to update from repository on server
>>>>
>>>> deb http://10.0.1.11/localrepository /
>>>>
>>>> Thank in advanse
> Here's the relevant information from the wiki:
>
> Solution 1: Use an HTTP proxy
>
> This solution is really easy to implement and is bandwidth efficient.
>
> Install a proxy server (i.e. squid) and then tell your freshclam clients to use it. This can be done by setting the HTTPProxyServer parameter in freshclam.conf (see man 5 freshclam.conf for the details).
>
> Solution 2: Serve .cvd files from a local web server
>
> This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you.
>
> Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files from http://database.clamav.net to the webserver's DocumentRoot.
>
> Add this line to freshclam.conf on machine1.mylan:
>
> ScriptedUpdates off
>
> First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on your clients so that it reads:
>
> DatabaseMirror machine1.mylan
>
> ScriptedUpdates off
>
> --
> Nigel Houghton
> Head Mentalist, Time Lord
> SF VRT Department of Intelligence Excellence
> http://vrt-blog.snort.org/&& http://labs.snort.org/
>
>
>
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


jesler at sourcefire

Jul 9, 2012, 4:43 AM

Post #5 of 9 (570 views)
Permalink
Re: update clamav [In reply to]

What issue?

--
Joel Esler

On Jul 9, 2012, at 5:08 AM, Bruno Barosa <bruno.barosa [at] pessoaseprocessos> wrote:

> Hello again,
>
> Good morning and a good week for all
>
> anyone has got news on this issue?
>
> Regards
> Bruno
>
> On 27-06-2012 19:29, Nigel Houghton wrote:
>> On Jun 27, 2012, at 8:12 AM, Matthew Olney wrote:
>>
>>> Apparently, the answer to this is on the wiki, but it is having issues.
>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Ilyas Doskhozhayev<idoskhozhayev [at] gmail>
>>>>> Date: June 27, 2012, 5:45:28 AM EDT
>>>>> To: jesler [at] sourcefire
>>>>> Subject: update clamav
>>>>>
>>>>> Hi thank all you team for this antivirus tool/
>>>>>
>>>>> My question is on debian i have servers that can not update virus database directly from internet, so they update from local repository on network
>>>>> So can i make clamav update from my local repository on server that has internet ?
>>>>>
>>>>>
>>>>> I use this source list to update from repository on server
>>>>>
>>>>> deb http://10.0.1.11/localrepository /
>>>>>
>>>>> Thank in advanse
>> Here's the relevant information from the wiki:
>>
>> Solution 1: Use an HTTP proxy
>>
>> This solution is really easy to implement and is bandwidth efficient.
>>
>> Install a proxy server (i.e. squid) and then tell your freshclam clients to use it. This can be done by setting the HTTPProxyServer parameter in freshclam.conf (see man 5 freshclam.conf for the details).
>>
>> Solution 2: Serve .cvd files from a local web server
>>
>> This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you.
>>
>> Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files from http://database.clamav.net to the webserver's DocumentRoot.
>>
>> Add this line to freshclam.conf on machine1.mylan:
>>
>> ScriptedUpdates off
>>
>> First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on your clients so that it reads:
>>
>> DatabaseMirror machine1.mylan
>>
>> ScriptedUpdates off
>>
>> --
>> Nigel Houghton
>> Head Mentalist, Time Lord
>> SF VRT Department of Intelligence Excellence
>> http://vrt-blog.snort.org/&& http://labs.snort.org/
>>
>>
>>
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>> http://www.clamav.net/support/ml
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


molney at sourcefire

Jul 9, 2012, 5:58 AM

Post #6 of 9 (599 views)
Permalink
Re: update clamav [In reply to]

Bruno,

Nigel Houghton replied on Jun 27th:

"Here's the relevant information from the wiki:

Solution 1: Use an HTTP proxy

This solution is really easy to implement and is bandwidth efficient.

Install a proxy server (i.e. squid) and then tell your freshclam
clients to use it. This can be done by setting the HTTPProxyServer
parameter in freshclam.conf (see man 5 freshclam.conf for the
details).

Solution 2: Serve .cvd files from a local web server

This solution is really simple to implement but it's only effective if
your clients are all on the same local network and bandwidth is not an
issue for you.

Configure a local webserver on one of your machines (say
machine1.mylan) and let freshclam download the *.cvd files from
http://database.clamav.net to the webserver’s DocumentRoot.

Add this line to freshclam.conf on machine1.mylan:

ScriptedUpdates off

First the database will be downloaded to the local webserver and then
the other clients on the network will update their copy of the
database from it. For this to work you have to change freshclam.conf
on your clients so that it reads:

DatabaseMirror machine1.mylan

ScriptedUpdates off"

Matt

On Mon, Jul 9, 2012 at 7:43 AM, Joel Esler <jesler [at] sourcefire> wrote:
> What issue?
>
> --
> Joel Esler
>
> On Jul 9, 2012, at 5:08 AM, Bruno Barosa <bruno.barosa [at] pessoaseprocessos> wrote:
>
>> Hello again,
>>
>> Good morning and a good week for all
>>
>> anyone has got news on this issue?
>>
>> Regards
>> Bruno
>>
>> On 27-06-2012 19:29, Nigel Houghton wrote:
>>> On Jun 27, 2012, at 8:12 AM, Matthew Olney wrote:
>>>
>>>> Apparently, the answer to this is on the wiki, but it is having issues.
>>>>
>>>>> Begin forwarded message:
>>>>>
>>>>>> From: Ilyas Doskhozhayev<idoskhozhayev [at] gmail>
>>>>>> Date: June 27, 2012, 5:45:28 AM EDT
>>>>>> To: jesler [at] sourcefire
>>>>>> Subject: update clamav
>>>>>>
>>>>>> Hi thank all you team for this antivirus tool/
>>>>>>
>>>>>> My question is on debian i have servers that can not update virus database directly from internet, so they update from local repository on network
>>>>>> So can i make clamav update from my local repository on server that has internet ?
>>>>>>
>>>>>>
>>>>>> I use this source list to update from repository on server
>>>>>>
>>>>>> deb http://10.0.1.11/localrepository /
>>>>>>
>>>>>> Thank in advanse
>>> Here's the relevant information from the wiki:
>>>
>>> Solution 1: Use an HTTP proxy
>>>
>>> This solution is really easy to implement and is bandwidth efficient.
>>>
>>> Install a proxy server (i.e. squid) and then tell your freshclam clients to use it. This can be done by setting the HTTPProxyServer parameter in freshclam.conf (see man 5 freshclam.conf for the details).
>>>
>>> Solution 2: Serve .cvd files from a local web server
>>>
>>> This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you.
>>>
>>> Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files from http://database.clamav.net to the webserver's DocumentRoot.
>>>
>>> Add this line to freshclam.conf on machine1.mylan:
>>>
>>> ScriptedUpdates off
>>>
>>> First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on your clients so that it reads:
>>>
>>> DatabaseMirror machine1.mylan
>>>
>>> ScriptedUpdates off
>>>
>>> --
>>> Nigel Houghton
>>> Head Mentalist, Time Lord
>>> SF VRT Department of Intelligence Excellence
>>> http://vrt-blog.snort.org/&& http://labs.snort.org/
>>>
>>>
>>>
>>> _______________________________________________
>>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>>> http://www.clamav.net/support/ml
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>> http://www.clamav.net/support/ml
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


bruno.barosa at pessoaseprocessos

Jul 9, 2012, 6:05 AM

Post #7 of 9 (590 views)
Permalink
Re: update clamav [In reply to]

Hi,

The issue is not beeing able to update the clamav "core".
Nigel posted about databse updates, if i understood it right.

I'm quoting my original post:

"
Hi, can anyone help?
Running on Centos 5.x (various versions from 5.4 to 5.8) 64bit.
Epel installed, RPMForge unninstalled, and prefer to keep it this way.

Logwatch:

Last ClamAV update process started at Thu Jun 21 04:02:02 2012

Last Status:
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.3 Recommended version: 0.97.5
DON'T PANIC! Readhttp://www.clamav.net/support/faq
main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)
daily.cld is up to date (version: 15065, sigs: 219026, f-level: 63, builder: guitar)
bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo)

The following ERRORS and/or WARNINGS were detected when
running the ClamAV update process. If these ERRORS and/or
WARNINGS do not show up in the "Last Status" section above,
then their underlying cause has probably been corrected.

WARNINGS:
Local version: 0.97.3 Recommended version: 0.97.5: 2 Time(s)
Your ClamAV installation is OUTDATED!: 2 Time(s)


-------------------------
Trying to update:

[root [at] myserve ~]# yum update clamav
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base:ftp.dei.uc.pt
* epel:ftp.rediris.es
* extras:ftp.dei.uc.pt
* updates:ftp.dei.uc.pt
base | 1.1 kB 00:00
epel | 3.4 kB 00:00
extras | 2.1 kB 00:00
updates | 1.9 kB 00:00
Setting up Update Process
No Packages marked for Update
[root [at] reticulu ~]# yum update clam*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base:ftp.dei.uc.pt
* epel:ftp.rediris.es
* extras:ftp.dei.uc.pt
* updates:ftp.dei.uc.pt
Setting up Update Process
No Packages marked for Update


Thanks

Bruno
"

Regards,
Bruno
**

On 09-07-2012 13:58, Matt Olney wrote:
> Bruno,
>
> Nigel Houghton replied on Jun 27th:
>
> "Here's the relevant information from the wiki:
>
> Solution 1: Use an HTTP proxy
>
> This solution is really easy to implement and is bandwidth efficient.
>
> Install a proxy server (i.e. squid) and then tell your freshclam
> clients to use it. This can be done by setting the HTTPProxyServer
> parameter in freshclam.conf (see man 5 freshclam.conf for the
> details).
>
> Solution 2: Serve .cvd files from a local web server
>
> This solution is really simple to implement but it's only effective if
> your clients are all on the same local network and bandwidth is not an
> issue for you.
>
> Configure a local webserver on one of your machines (say
> machine1.mylan) and let freshclam download the *.cvd files from
> http://database.clamav.net to the webserver’s DocumentRoot.
>
> Add this line to freshclam.conf on machine1.mylan:
>
> ScriptedUpdates off
>
> First the database will be downloaded to the local webserver and then
> the other clients on the network will update their copy of the
> database from it. For this to work you have to change freshclam.conf
> on your clients so that it reads:
>
> DatabaseMirror machine1.mylan
>
> ScriptedUpdates off"
>
> Matt
>
> On Mon, Jul 9, 2012 at 7:43 AM, Joel Esler<jesler [at] sourcefire> wrote:
>> What issue?
>>
>> --
>> Joel Esler
>>
>> On Jul 9, 2012, at 5:08 AM, Bruno Barosa<bruno.barosa [at] pessoaseprocessos> wrote:
>>
>>> Hello again,
>>>
>>> Good morning and a good week for all
>>>
>>> anyone has got news on this issue?
>>>
>>> Regards
>>> Bruno
>>>
>>> On 27-06-2012 19:29, Nigel Houghton wrote:
>>>> On Jun 27, 2012, at 8:12 AM, Matthew Olney wrote:
>>>>
>>>>> Apparently, the answer to this is on the wiki, but it is having issues.
>>>>>
>>>>>> Begin forwarded message:
>>>>>>
>>>>>>> From: Ilyas Doskhozhayev<idoskhozhayev [at] gmail>
>>>>>>> Date: June 27, 2012, 5:45:28 AM EDT
>>>>>>> To: jesler [at] sourcefire
>>>>>>> Subject: update clamav
>>>>>>>
>>>>>>> Hi thank all you team for this antivirus tool/
>>>>>>>
>>>>>>> My question is on debian i have servers that can not update virus database directly from internet, so they update from local repository on network
>>>>>>> So can i make clamav update from my local repository on server that has internet ?
>>>>>>>
>>>>>>>
>>>>>>> I use this source list to update from repository on server
>>>>>>>
>>>>>>> deb http://10.0.1.11/localrepository /
>>>>>>>
>>>>>>> Thank in advanse
>>>> Here's the relevant information from the wiki:
>>>>
>>>> Solution 1: Use an HTTP proxy
>>>>
>>>> This solution is really easy to implement and is bandwidth efficient.
>>>>
>>>> Install a proxy server (i.e. squid) and then tell your freshclam clients to use it. This can be done by setting the HTTPProxyServer parameter in freshclam.conf (see man 5 freshclam.conf for the details).
>>>>
>>>> Solution 2: Serve .cvd files from a local web server
>>>>
>>>> This solution is really simple to implement but it's only effective if your clients are all on the same local network and bandwidth is not an issue for you.
>>>>
>>>> Configure a local webserver on one of your machines (say machine1.mylan) and let freshclam download the *.cvd files from http://database.clamav.net to the webserver's DocumentRoot.
>>>>
>>>> Add this line to freshclam.conf on machine1.mylan:
>>>>
>>>> ScriptedUpdates off
>>>>
>>>> First the database will be downloaded to the local webserver and then the other clients on the network will update their copy of the database from it. For this to work you have to change freshclam.conf on your clients so that it reads:
>>>>
>>>> DatabaseMirror machine1.mylan
>>>>
>>>> ScriptedUpdates off
>>>>
>>>> --
>>>> Nigel Houghton
>>>> Head Mentalist, Time Lord
>>>> SF VRT Department of Intelligence Excellence
>>>> http://vrt-blog.snort.org/&& http://labs.snort.org/
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>>>> http://www.clamav.net/support/ml
>>> _______________________________________________
>>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>>> http://www.clamav.net/support/ml
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
>> http://www.clamav.net/support/ml
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


kdeugau at vianet

Jul 9, 2012, 7:58 AM

Post #8 of 9 (567 views)
Permalink
Re: update clamav [In reply to]

Bruno Barosa wrote:
> Hi,
>
> The issue is not beeing able to update the clamav "core".
> Nigel posted about databse updates, if i understood it right.
>
> I'm quoting my original post:
>
> "
> Hi, can anyone help?
> Running on Centos 5.x (various versions from 5.4 to 5.8) 64bit.
> Epel installed, RPMForge unninstalled, and prefer to keep it this way.

And as previously responded, you have 3 choices to keep the Clam
software up to date if you don't want to use RPMForge:

-> Wait for EPEL to update their Clamav package(s)

-> Take an existing source package and rebuild for the current Clamav
release

-> Uninstall the packages and install straight from source

(There may be other groups building addon packages for RHEL and its
community rebuilds; I haven't bothered looking since RPMForge works for
me.)

If you absolutely have to get the current version, and you can't build
from source (either straight source install or package rebuild), and you
don't want to use the RPMForge package, you'll have to bug the EPEL
folks for an updated package.

I used to build my own packages for quite a few things before I came
across Dag Wieers' efforts a number of years ago (which have since been
brought under the RPMForge umbrella), and aside from some personal
preference issues with how they've declared dependencies on some of the
more complex Perl(-using) packages (MIMEDefang and SpamAssassin) I
haven't had any issues with their packages.

-kgd
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml


me at junc

Jul 9, 2012, 8:01 AM

Post #9 of 9 (566 views)
Permalink
Re: update clamav [In reply to]

Den 2012-07-09 15:05, Bruno Barosa skrev:

> The issue is not beeing able to update the clamav "core".
> Nigel posted about databse updates, if i understood it right.

if 0.97.4 and 0.97.5 is stable why not tell package maintainers on
centos about it ?

0.97.3 is still latest stable on gentoo/funtoo


_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

ClamAV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.