Re: [clamav-users] Daily 23161 broke Clam

In Debian we back port security fixes the same way, but libraries with different SO names are co-installable, so there's generally ways to deal with these things. Clamav itself is an exception since not keeping up in functionality means you lose the arms race. Scott K On March 3, 2017 7:04:03

Re: [clamav-users] Daily 23161 broke Clam

Hello, Insist :) Well, its considered bad practice to upgrade packages independently on a RH-based system where dependancies break. Security fixes are back-ported to older versions to preserve versioning an compatibility. Thats a Redhat feature I agree, and RHEL5 will be EOL in 28 days, so

Re: [clamav-users] Daily 23161 broke Clam

As far as I can tell, pcre 7 came out before 2008. I think a decade is enough time to insist people upgrade. Scott K On Friday, March 03, 2017 11:21:30 PM Joel Esler wrote: > If we required pcre 7, it would allow us to publish this kind of sig in the > future of 99.3 and high versions by

Re: [clamav-users] Daily 23161 broke Clam

If we required pcre 7, it would allow us to publish this kind of sig in the future of 99.3 and high versions by requiring a certain "flevel". -- Sent from my iPhone > On Mar 3, 2017, at 18:18, Chris Conn wrote: > > Hello, > > Looks like my off-list email went on the list

Re: [clamav-users] Daily 23161 broke Clam

Hello, Looks like my off-list email went on the list LOL. So much for not making noise. Woops. If the 0.99.3 or whatever later version where this would be implemented requires PCRE 7, would that break database updates for versions that have not upgraded if this pcre format is re-used in

Re: [clamav-users] Daily 23161 broke Clam

A new daily with the Sig dropped. Probably what we will do to prevent this from happening again, is to have 0.99.3 (the upcoming version) require pcre 7. How does that sound? -- Sent from my iPhone > On Mar 3, 2017, at 18:08, Chris Conn wrote: > > Hello, > > I hope you

Re: [clamav-users] Daily 23161 broke Clam

Hello, I hope you don't mind my contact off-list, I don't want to make noise on it for all. Apologies. This new build, are we talking about a daily.cvd (23162?) or a new build of clam/pcre? Thanks again in advance for your help, Chris On 3/3/2017 4:00 PM, Alain Zidouemba wrote: We are

Re: [clamav-users] Daily 23161 broke Clam

thanks for this build because i have the same problem with pcre in rel5 Now, I think it will be necessary to quickly update the servers ;-) regards Le 03/03/2017 à 22:00, Alain Zidouemba a écrit : We are coming to the same conclusions. The issue seem to isolated to using pcre libraries

[clamav-users] Releasing quarantined files

I am running updated Fedora 25. I have Clamav-milter working. I used a test virus and it was quarantined. It is in /var/spool/mqueue. I can see it with this command. fc25> mailq -qQ /var/spool/mqueue (1 request) -Q-ID- --Size-- -Q-Time-

Re: [clamav-users] Any way to force scan as mail?

On Mar 2, 2017, at 10:43 AM, G.W. Haywood wrote: I reject everything from Hotmail (and Yahoo, Comcast, RR, Gmail and a couple of dozen other fairly big 'free' email providers) because that is much more effective and much less demanding on CPU+RAM than trying to sift

Re: [clamav-users] Daily 23161 broke Clam

We are coming to the same conclusions. The issue seem to isolated to using pcre libraries older than 7.0. I does not affect users of newer versions of pcre or users of pcre2. A new build with the fix is in progress now. Apologies for the impact this has caused. Alain On Fri, Mar 3, 2017 at

Re: [clamav-users] Daily 23161 broke Clam

Hello, That may be true, but you also have to maintain a self-compiled version of clamav now, and future updates you will need to re-do this. This may be satisfactory to you as I don't of course know or understand your particular situation, but for the clamav userbase that is using RHEL5

Re: [clamav-users] Daily 23161 broke Clam

Em 03/03/17 17:31, Chris Conn escreveu: Updating the PCRE manually doesn't seem like an option as it will break dependancies for important packages, grep, php and httpd among others. I had success installing new PCRE libs on /usr/local (thus keeping system libraries untouched) and

Re: [clamav-users] Daily 23161 broke Clam

Hello, If I can add to this discussion; since daily 23161 some RHEL5 systems (pcre-6.6-9) are failing with that same error. A number of them have down clamd at the moment. Updating the PCRE manually doesn't seem like an option as it will break dependancies for important packages, grep, php

Re: [clamav-users] Daily 23161 broke Clam

I said in a previous mail, that i had the problem on CentOS 6 boxes, and that's not true, sorry for that. All my CentOS 6 boxes are OK, and they have latest pcre from CentOS: [root@correio ~]# rpm -qa | grep pcre pcre-devel-7.8-7.el6.x86_64 pcre-7.8-7.el6.x86_64 The boxes on CentOS

Re: [clamav-users] Daily 23161 broke Clam

Hi Aaron and Leonardo, What are the versions of libpcre on your systems? Thanks, Steve ___ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV

Re: [clamav-users] Daily 23161 broke Clam

On Fri, March 3, 2017 7:20 pm, Alain Zidouemba wrote: > We're pulling the signature causing the issue now, while we investigate > the cause. > > - Alain Hi Alain, I think the fix is... Replace ? with ?P when the PCRE library is old ie. ?< to ?P< On... Doc.Macro.GenericHeuristic-5901772-0

Re: [clamav-users] Daily 23161 broke Clam

We're pulling the signature causing the issue now, while we investigate the cause. - Alain On Fri, Mar 3, 2017 at 12:38 PM, Aaron C. Bolch wrote: > Greetings, > > After Daily Update 23161 was applied, the following error happened: > > Database initialization error: can’t

Re: [clamav-users] Daily 23161 broke Clam

OK, so it's PCRE related. Compiling new PCRE libs and linking clamav to it should solve the problem, that's right ? Em 03/03/17 15:11, Steve Basford escreveu: It's a macro detecting ldb Sig that fails due to an old pcre engine being used. The Sig can be rewritten to work on older pcre

Re: [clamav-users] Daily 23161 broke Clam

It's a macro detecting ldb Sig that fails due to an old pcre engine being used. The Sig can be rewritten to work on older pcre versions .. or you need to update. Sorry I can't help more. Cheers, Steve Twitter: @sanesecurity On 3 March 2017 17:39:48 "Aaron C. Bolch"

Re: [clamav-users] Daily 23161 broke Clam

Same problem here with 0.99.2 on CentOS 6 machine: [root@correio clamav]# service clamd start Starting Clam AV daemon: LibClamAV Error: cli_pcre_compile: PCRE compilation failed at offset 52: unrecognized character after (?< LibClamAV Error: cli_pcre_build: failed to build pcre regex

[clamav-users] Daily 23161 broke Clam

Greetings, After Daily Update 23161 was applied, the following error happened: Database initialization error: can’t compile engine: Malformed Database When starting Clamd: LibCLamAV Error: cli_pcre_compile: PCRE compilation failed at offset 52: unrecognized character after (?< LibClamAV

Re: [clamav-users] Any way to force scan as mail?

Hi there, On Fri, 3 Mar 2017, Reindl Harald wrote: ... do yourself a favour and click on the "raw" link Click? My mail client is called 'Alpine'. It doesn't do 'click'. ... that's a pure raw-eml with nothing HTMLified But still not the original problem message... -- 73, Ged.