Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
On Mon, 08 Sep 2008 18:00:19 -0500 René Berber [EMAIL PROTECTED] wrote: The idea of Cygwin is to be able to build with the same sources used under Linux. Of course there are problem areas, those are few, and the Cygwin maintainers/package porters should take care of them. My recommendation for ClamAV is to get rid of all the #ifdef CL_CYGWIN blocks, and any others related to Cygwin. This is what we did in 0.94. We simply dropped the special support for Cygwin (that is all Cygwin related code entries) as this code was not working properly. The major problem here was similar to the one described in my previous message. If something was not working with a particular version of the Cygwin DLL and we implemented a work-around for the issue then a little while later it was turning out that this workaround is not compatible with a new version of Cygwin. This definitely wasn't the way to go. This morning I was doing various tests of ClamAV 0.93.1 provided by Cygwin. I must say the results were pretty much surprising to me as I didn't find any problems (1+ infected files in various formats got detected properly; also there were no false positives). Now I'm curious how 0.94 (which comes without any special Cygwin code) would pass the same test. A native build will not work with Exim (which has sections written explicitly for Cygwin and builds out of the box, just like ClamAV) or any other application that uses sockets; the socket file is not compatible with native applications. Doesn't the AV code in Exim support TCP sockets? -- oo. Tomasz Kojm [EMAIL PROTECTED] (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Tue Sep 9 12:15:08 CEST 2008 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] Clamav 0.94 for AIX 5.2, AIX5.3 and AIX 6.1.
Could anyone please advise of a download site for the binary program for Clamav 0.94 for AIX 5.2, AIX5.3 and AIX 6.1. Thank You ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
On Thu, 04 Sep 2008 18:14:24 -0500 René Berber [EMAIL PROTECTED] wrote: Do we get back support for Cygwin? Hello René, we generally had not so good experience with Cygwin based builds of ClamAV over the past few years. The most common problem was different detection results depending on the versions of cygwin dlls used (eg. sometimes older dlls performed better than the latest ones, etc.). We got a lot of reports for such issues and spent too much time looking for problems in ClamAV which didn't really exist... We find the native builds much more reliable (and of course many times faster) and very likely will start providing the win32 binaries with ClamAV 0.95. Thanks, -- oo. Tomasz Kojm [EMAIL PROTECTED] (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Mon Sep 8 11:58:22 CEST 2008 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] Clamav 0.94
Hi , I have a mail server with : Debian etch Postfix Mailscanner Clamav Yesterday it work fine catching virus, but todat i've made an upgrade from clamav 0.93 to 0.94 and then the process stop catching mail with virus, i mean , the mails are stoped anyway by No programs allowed with mailscanner because of the extensions file, but there is not any message or report from ClamAv. I have a txt file with eicar string , if i run on server: cat filewitheicar.txt | mail [EMAIL PROTECTED] the mail pass through the mailscanner and the workstation's antivirus alert me abourt the eicar strings. Why the mailscanner stop using clamav? Thank you any help about this. Sorry about my english Jose Julian Buda ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
Jose Julian Buda wrote: Hi , I have a mail server with : Debian etch Postfix Mailscanner Clamav Yesterday it work fine catching virus, but todat i've made an upgrade from clamav 0.93 to 0.94 and then the process stop catching mail with virus, i mean , the mails are stoped anyway by No programs allowed with mailscanner because of the extensions file, but there is not any message or report from ClamAv. I have a txt file with eicar string , if i run on server: cat filewitheicar.txt | mail [EMAIL PROTECTED] Try using clamscan filewitheicar.txt If clamscan detects the virus, then the problem is with your mailscanner config. If clamscan by itself _does_not_ detect the test file, then something is terribly wrong with your clamscan, and your problem has nothing to do with mailscanner. the mail pass through the mailscanner and the workstation's antivirus alert me abourt the eicar strings. Why the mailscanner stop using clamav? First make sure clamscan by itself works as expected. Then you know it's a mailscanner problem. Maybe clamscan installed to a different path than mailscanner expects. Maybe mailscanner is configured to use some no-longer-valid command line switch. Check your mailscanner logs and/or ask on a mailscanner support forum. -- Noel Jones ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
- Original Message - From: Noel Jones [EMAIL PROTECTED] To: ClamAV users ML clamav-users@lists.clamav.net Sent: Monday, September 08, 2008 1:54 PM Subject: Re: [Clamav-users] Clamav 0.94 Jose Julian Buda wrote: Hi , I have a mail server with : Debian etch Postfix Mailscanner Clamav Yesterday it work fine catching virus, but todat i've made an upgrade from clamav 0.93 to 0.94 and then the process stop catching mail with virus, i mean , the mails are stoped anyway by No programs allowed with mailscanner because of the extensions file, but there is not any message or report from ClamAv. I have a txt file with eicar string , if i run on server: cat filewitheicar.txt | mail [EMAIL PROTECTED] Try using clamscan filewitheicar.txt If clamscan detects the virus, then the problem is with your mailscanner config. If clamscan by itself _does_not_ detect the test file, then something is terribly wrong with your clamscan, and your problem has nothing to do with mailscanner. the mail pass through the mailscanner and the workstation's antivirus alert me abourt the eicar strings. Why the mailscanner stop using clamav? First make sure clamscan by itself works as expected. Then you know it's a mailscanner problem. Maybe clamscan installed to a different path than mailscanner expects. Maybe mailscanner is configured to use some no-longer-valid command line switch. Check your mailscanner logs and/or ask on a mailscanner support forum. -- Noel Jones ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml __ Información de NOD32, revisión 3424 (20080907) __ Este mensaje ha sido analizado con NOD32 antivirus system http://www.nod32.com proxymails:~# clamscan filewitheicar.txt filewitheicar.txt: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 416228 Engine version: 0.94 Scanned directories: 0 Scanned files: 1 Infected files: 1 Data scanned: 0.00 MB Time: 2.187 sec (0 m 2 s) proxymails:~# I do not change anything in the mailscanner config file, i just upgrade the clamav. How can i debug this error? Thank you Jose Julian Buda ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
Jose Julian Buda wrote: proxymails:~# clamscan filewitheicar.txt filewitheicar.txt: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 416228 Engine version: 0.94 Scanned directories: 0 Scanned files: 1 Infected files: 1 Data scanned: 0.00 MB Time: 2.187 sec (0 m 2 s) proxymails:~# I do not change anything in the mailscanner config file, i just upgrade the clamav. How can i debug this error? OK, it appears that clamscan is working correctly; mailscanner isn't. Check your mailscanner logs and/or ask on a mailscanner support forum. Maybe clamscan installed to a different path than mailscanner expects. Maybe mailscanner is configured to use some no-longer-valid command line switch. Hopefully mailscanner will log any errors returned by clamscan. -- Noel Jones ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
Noel Jones wrote: Jose Julian Buda wrote: proxymails:~# clamscan filewitheicar.txt filewitheicar.txt: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 416228 Engine version: 0.94 Scanned directories: 0 Scanned files: 1 Infected files: 1 Data scanned: 0.00 MB Time: 2.187 sec (0 m 2 s) proxymails:~# I do not change anything in the mailscanner config file, i just upgrade the clamav. How can i debug this error? OK, it appears that clamscan is working correctly; mailscanner isn't. perhaps clamscan is working but clamdscan is not working ? Regards, Rick ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
- Original Message - From: Rick Macdougall [EMAIL PROTECTED] To: ClamAV users ML clamav-users@lists.clamav.net Sent: Monday, September 08, 2008 2:14 PM Subject: Re: [Clamav-users] Clamav 0.94 Noel Jones wrote: Jose Julian Buda wrote: proxymails:~# clamscan filewitheicar.txt filewitheicar.txt: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Known viruses: 416228 Engine version: 0.94 Scanned directories: 0 Scanned files: 1 Infected files: 1 Data scanned: 0.00 MB Time: 2.187 sec (0 m 2 s) proxymails:~# I do not change anything in the mailscanner config file, i just upgrade the clamav. How can i debug this error? OK, it appears that clamscan is working correctly; mailscanner isn't. perhaps clamscan is working but clamdscan is not working ? Regards, Rick ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml __ Información de NOD32, revisión 3424 (20080907) __ Este mensaje ha sido analizado con NOD32 antivirus system http://www.nod32.com proxymails:~# clamdscan filewitheicar.txt /root/filewitheicar.txt: Eicar-Test-Signature FOUND --- SCAN SUMMARY --- Infected files: 1 Time: 0.064 sec (0 m 0 s) proxymails:~# clamdscan seems to work fine, so clamd is running properly am i right? you mean it`s a mailscanner problem? Thank you Jose Jlian Buda ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
Jose Julian Buda wrote: you mean it`s a mailscanner problem? Thank you Jose Jlian Buda Yes, it's a mailscanner problem. I suspect that mailscanner is using some no-longer-valid command line switch with clamscan, but that's just a wild guess. Mailscanner does not use clamd or clamdscan unless you've altered it to do so. Check your mailscanner logs or ask for help on a mailscanner support forum. -- Noel Jones ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Tomasz Kojm wrote: On Thu, 04 Sep 2008 18:14:24 -0500 René Berber [EMAIL PROTECTED] wrote: Do we get back support for Cygwin? Hello René, we generally had not so good experience with Cygwin based builds of ClamAV over the past few years. The most common problem was different detection results depending on the versions of cygwin dlls used (eg. sometimes older dlls performed better than the latest ones, etc.). We got a lot of reports for such issues and spent too much time looking for problems in ClamAV which didn't really exist... We find the native builds much more reliable (and of course many times faster) and very likely will start providing the win32 binaries with ClamAV 0.95. By support I meant getting answers on this list, nothing more. The idea of Cygwin is to be able to build with the same sources used under Linux. Of course there are problem areas, those are few, and the Cygwin maintainers/package porters should take care of them. My recommendation for ClamAV is to get rid of all the #ifdef CL_CYGWIN blocks, and any others related to Cygwin. A native build will not work with Exim (which has sections written explicitly for Cygwin and builds out of the box, just like ClamAV) or any other application that uses sockets; the socket file is not compatible with native applications. Thanks for taking time to reply. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Clamav 0.94
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noel Jones Sent: Monday, September 08, 2008 2:31 PM To: ClamAV users ML Subject: Re: [Clamav-users] Clamav 0.94 Jose Julian Buda wrote: you mean it`s a mailscanner problem? Thank you Jose Jlian Buda Yes, it's a mailscanner problem. I suspect that mailscanner is using some no-longer-valid command line switch with clamscan, but that's just a wild guess. Mailscanner does not use clamd or clamdscan unless you've altered it to do so. Check your mailscanner logs or ask for help on a mailscanner support forum. MailScanner has used clamd directly, (no script, no perl module) for many months now, it is the preferred method by many, many SAs. Rick -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Török Edwin wrote:
[snip]
I built 0.94rc1 myself on cygwin, and confirmed this.
For some reason lstat() works with 0.94 ... after we dropped cygwin support.
Weird isn't it?
No, programming is deterministic, something changed in the code.
My guess is that one of the C_CYGWIN portions of code actually made
things worse, and caused clamdscan to fail.
But nobody noticed, until now, when we added unit tests.
Found it, I told you it was non-sense:
In file clamdscan/client.c at line 251, as you said, there's a C_CYGWIN
section... which to me makes no sense, so I commented it out,
//#ifdef C_CYGWIN
// sprintf(fullpath, %s, filename);
//#else
if(!getcwd(cwd, PATH_MAX)) {
logg(^Can't get absolute pathname of current working
directory.\n);
return NULL;
}
sprintf(fullpath, %s/%s, cwd, filename);
//#endif
Now, re-testing (clamd is 0.94 but it doesn't matter, I tested before
and after the change, before fails, after works... OK, I'll show both
tests).
$ ../clamdscan/clamdscan -h
ClamAV Daemon Client 0.94rc1
...
(I used -h since -V shows the daemon version -- more weirdness)
$ ../clamdscan/clamdscan clam.exe
clam.exe: lstat() failed. ERROR
$ vi client.c
... commented out the lines ...
$ cd ..
$ make
... (only client.c was recompiled and clamdscan relinked)
$ ../clamdscan/clamdscan clam.exe
/home/rberber/Projects/clamav-0.94rc1/test/clam.exe: ClamAV-Test-File FOUND
--- SCAN SUMMARY ---
Infected files: 1
Time: 0.139 sec (0 m 0 s)
Do we get back support for Cygwin?
--
René Berber
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
On 2008-09-03 01:39, René Berber wrote: Brandon Perry wrote: IIRC, the announcement said that POSIX breakage would happen if you tried to compile 0.94 on cygwin... If you mean this part : ** This version drops the special support for Cygwin. Our QA process showed ** serious problems with ClamAV builds under Cygwin due to some low-level ** incompatibilities in the POSIX compatibility layer, resulting in unreliable ** ClamAV behaviour. It sounds like non-sense to me, version 0.94rc1 works fine, and both versions build fine. The above statement seems to come from somebody that didn't even test, didn't look at what 'make check' was doing, and didn't really care. serious problems ? Only problem is the test I mentioned, passing a file descriptor is not supported under Cygwin as far as I know. No, file descriptor passing is not a 'critical' feature, and is not the reason for dropping Cygwin. Passing file descriptors among arbitrary processes can't work on Windows because it is not supported by the OS, it only works on systems supporting Unix domain sockets. [of course file desc passing works across fork(), but that is not the point here] This is not cygwin's fault, and there isn't anything cygwin could do about it. unreliable behaviour ? Does that mean the distribution/use of older bzip2 libraries? The warning at configure time is clear, I'm not sure it is correct, the CVE says before 1.0.5, Cygwin uses 1.0.5 . And the gem: incompatibilties in ... compatibility layer; it is or it isn't compatible? The Cygwin folks make an effort for being POSIX compatible. Have a look at bb #1139 for an example: lstat() failing for no apparent reason. Try 'clamdscan ../test/clam.exe' vs. 'clamdscan clam.exe'. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Solaris 9
On 2008-09-03 04:09, René Berber wrote: Hello, Sorry for the long post. The following command and error stops clamav build, any ideas? gcc -shared -Wl,-h -Wl,libclamav.so.5 -o .libs/libclamav.so.5.0.1 .libs/matcher-ac.o .libs/matcher-bm.o .libs/matcher.o .libs/md5.o .libs/others.o .libs/readdb.o .libs/cvd.o .libs/dsig.o .libs/str.o .libs/scanners.o .libs/textdet.o .libs/filetypes.o .libs/rtf.o .libs/blob.o .libs/mbox.o .libs/message.o .libs/table.o .libs/text.o .libs/ole2_extract.o .libs/vba_extract.o .libs/msexpand.o .libs/pe.o .libs/disasm.o .libs/upx.o .libs/htmlnorm.o .libs/chmunpack.o .libs/rebuildpe.o .libs/petite.o .libs/wwunpack.o .libs/unsp.o .libs/aspack.o .libs/packlibs.o .libs/fsg.o .libs/mew.o .libs/upack.o .libs/line.o .libs/untar.o .libs/unzip.o .libs/inflate64.o .libs/special.o .libs/binhex.o .libs/is_tar.o .libs/tnef.o .libs/autoit.o .libs/strlcpy.o .libs/regcomp.o .libs/regerror.o .libs/regexec.o .libs/regfree.o .libs/unarj.o .libs/bzlib.o .libs/nulsft.o .libs/infblock.o .libs/pdf.o .libs/spin.o .libs/yc.o .libs/elf.o .libs/sis.o .libs/uuencode.o .libs/phishcheck.o .libs/phish_domaincheck_db.o .libs/phish_whitelist.o .libs/regex_list.o .libs/regex_suffix.o .libs/mspack.o .libs/cab.o .libs/entconv.o .libs/hashtab.o .libs/dconf.o .libs/lzma_iface.o .libs/explode.o .libs/textnorm.o .libs/dlp.o .libs/js-norm.o .libs/uniq.o .libs/version.o -Wl,-z -Wl,allextract lzma/.libs/liblzma.a -Wl,-z -Wl,defaultextract -R/usr/share/src/clamav-0.94/libclamunrar_iface/.libs -R/usr/local/lib -R/usr/local/lib ../libclamunrar_iface/.libs/libclamunrar_iface.so -L/usr/share/src/clamav-0.94/libclamunrar/.libs -L/usr/local/lib -lz -lbz2 /usr/local/lib/libgmp.so /usr/local/lib/libiconv.so -L/usr/lib -L/usr/openwin/lib -L/usr/local/ssl/lib -L/usr/local/BerkeleyDB.4.2/lib -lpthread -lnsl -lsocket -lc -Wl,-M -Wl,../libclamav/libclamav.map ld: fatal: ../libclamav/libclamav.map: 109: symbol `uniq_get' is already defined in file: ../libclamav/libclamav.map The file libclamav.map does indeed have uniq_get twice, I can't find where the duplicate comes from, it's not duplicated on clamav's code. Please remove one of the 'uniq_get' entries in libclamav.map. On 2008-09-03 08:00, René Berber wrote: Additional info: gcc is version 3.4.6, ld in not GNU ld, it is Sun's version 5.9-1.378 . In fact, ld's -M parameter seems to have different meaning, and it also could be a bug (ld itself added the symbol twice). Hmm, it built on Solaris 10 just fine, looks like your ld is stricter. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Török Edwin wrote: [snip] Have a look at bb #1139 for an example: lstat() failing for no apparent reason. The problems with lstat() are well known, and it doesn't fail randomly. But your point is that it affects clamav; I have never seen that particular failure, and I test clamscan/clamdscan/freshclam every time I install a new version (with the contents of the test directory). The bug #1139 mentions the same part I proposed to fix on checking, killing the daemon does not clear the socket, so I just added a remove before test; simple and besides in Cygwin we don't run the daemon directly, is controlled by cygrunsrv which sends the correct signal. Try 'clamdscan ../test/clam.exe' vs. 'clamdscan clam.exe'. $ uname -a CYGWIN_NT-5.1 black 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin $ clamdscan -V ClamAV 0.94/8145/Wed Sep 3 01:00:57 2008 $ clamdscan clam.exe /home/rberber/Projects/clamav-0.94/test/clam.exe: ClamAV-Test-File FOUND --- SCAN SUMMARY --- Infected files: 1 Time: 0.109 sec (0 m 0 s) $ clamdscan ../test/clam.exe /home/rberber/Projects/clamav-0.94/test/../test/clam.exe: ClamAV-Test-File FOUND --- SCAN SUMMARY --- Infected files: 1 Time: 0.109 sec (0 m 0 s) What is supposed to not do? Or you meant run it continuously until it fails? -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Solaris 9
Török Edwin wrote: [snip] Please remove one of the 'uniq_get' entries in libclamav.map. That worked, thanks. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
René Berber wrote: The problems with lstat() are well known, and it doesn't fail randomly. Oops! sorry, lstat() doesn't have problems, I was thinking of lseek(). If a lstat() problem was reported the usual cause is (just like in Unix/Linux): 1. Permission problems; 2. File system problems (i.e. network drive, NFS mount, disk format that doesn't support permissions which means Win95 format or DOS format). My conclusion is that you are dropping support based on a report from an inexperienced user. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
On 2008-09-03 13:07, René Berber wrote: $ clamdscan ../test/clam.exe /home/rberber/Projects/clamav-0.94/test/../test/clam.exe: ClamAV-Test-File FOUND --- SCAN SUMMARY --- Infected files: 1 Time: 0.109 sec (0 m 0 s) What is supposed to not do? Or you meant run it continuously until it fails? Try the same with 0.94rc1, it doesn't work with relative paths, it shows: ../test/clam.exe: lstat() failed. ERROR I built 0.94rc1 myself on cygwin, and confirmed this. For some reason lstat() works with 0.94 ... after we dropped cygwin support. Weird isn't it? Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Török Edwin wrote: [snip] Try the same with 0.94rc1, it doesn't work with relative paths, it shows: ../test/clam.exe: lstat() failed. ERROR Nope, clamdscan doesn't work at all : $ clamdscan -V ClamAV 0.94rc1/8145/Wed Sep 3 01:00:57 2008 $ clamdscan clam.exe clam.exe: lstat() failed. ERROR $ clamdscan ../test/clam.exe ../test/clam.exe: lstat() failed. ERROR Sorry I missed this, I just put it in operation with Exim and clamdmon and saw no problems. Of course Exim does not use clamdscan, it communicates directly to clamd, so clamdscan was never tested; I did test clamscan. The above behaviour usually means permission problems, clamd is running as user SYSTEM but not even in a SYSTEM owned directory (exim's spool) the test works... I built 0.94rc1 myself on cygwin, and confirmed this. For some reason lstat() works with 0.94 ... after we dropped cygwin support. Weird isn't it? No, programming is deterministic, something changed in the code. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
On 2008-09-03 22:54, René Berber wrote: Török Edwin wrote: [snip] Try the same with 0.94rc1, it doesn't work with relative paths, it shows: ../test/clam.exe: lstat() failed. ERROR Nope, clamdscan doesn't work at all : $ clamdscan -V ClamAV 0.94rc1/8145/Wed Sep 3 01:00:57 2008 $ clamdscan clam.exe clam.exe: lstat() failed. ERROR $ clamdscan ../test/clam.exe ../test/clam.exe: lstat() failed. ERROR Sorry I missed this, I just put it in operation with Exim and clamdmon and saw no problems. Of course Exim does not use clamdscan, it communicates directly to clamd, so clamdscan was never tested; I did test clamscan. The above behaviour usually means permission problems, clamd is running as user SYSTEM but not even in a SYSTEM owned directory (exim's spool) the test works... I built 0.94rc1 myself on cygwin, and confirmed this. For some reason lstat() works with 0.94 ... after we dropped cygwin support. Weird isn't it? No, programming is deterministic, something changed in the code. My guess is that one of the C_CYGWIN portions of code actually made things worse, and caused clamdscan to fail. But nobody noticed, until now, when we added unit tests. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] ClamAV 0.94 release
On Ubuntu 8.04, make check fails with: gcc -DSRCDIR=\/root/clamav-0.94/unit_tests\ -g -O2 -o .libs/check_clamav check_clamav-check_clamav.o check_clamav-check_jsnorm.o check_clamav-check_str.o check_clamav-check_regex.o check_clamav-check_disasm.o check_clamav-check_uniq.o check_clamav-check_matchers.o ../libclamav/.libs/libclamav.so -lpthread -lcheck -lz /usr/bin/ld: cannot find -lcheck collect2: ld returned 1 exit status make[2]: *** [check_clamav] Error 1 make[2]: Leaving directory `/root/clamav-0.94/unit_tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/root/clamav-0.94/unit_tests' make: *** [check-recursive] Error 1 Compiles fine obviously. After doing make uninstall and make install, running freshclam says that I am still running 0.94-exp, not 0.94. Running freshclam from the source dir says the same thing: [EMAIL PROTECTED]:~/clamav-0.94/freshclam$ ./freshclam ClamAV update process started at Tue Sep 2 16:03:03 2008 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.94-exp Recommended version: 0.94 DON'T PANIC! Read http://www.clamav.net/support/faq main.cvd is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven) Trying host database.clamav.net (209.170.150.7)... [EMAIL PROTECTED]:~/clamav-0.94/freshclam$ -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
On 2008-09-02 19:06, Brandon Perry wrote: On Ubuntu 8.04, make check fails with: gcc -DSRCDIR=\/root/clamav-0.94/unit_tests\ -g -O2 -o .libs/check_clamav check_clamav-check_clamav.o check_clamav-check_jsnorm.o check_clamav-check_str.o check_clamav-check_regex.o check_clamav-check_disasm.o check_clamav-check_uniq.o check_clamav-check_matchers.o ../libclamav/.libs/libclamav.so -lpthread -lcheck -lz /usr/bin/ld: cannot find -lcheck collect2: ld returned 1 exit status make[2]: *** [check_clamav] Error 1 make[2]: Leaving directory `/root/clamav-0.94/unit_tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/root/clamav-0.94/unit_tests' make: *** [check-recursive] Error 1 Run apt-get install check. Compiles fine obviously. After doing make uninstall and make install, running freshclam says that I am still running 0.94-exp, not 0.94. Running freshclam from the source dir says the same thing: Did you configure with --enable-experimental? Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
Ok, make check works. valgrind check fails, but that is't an issue to me. On Tue, Sep 2, 2008 at 11:11 AM, Brandon Perry [EMAIL PROTECTED]wrote: Run apt-get install check. Compiles fine obviously. After doing make uninstall and make install, running freshclam says that I am still running 0.94-exp, not 0.94. Running freshclam from the source dir says the same thing: Did you configure with --enable-experimental? Yes, I used --enable-experimental ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml -- http://www.volatileminds.net -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
Run apt-get install check. Compiles fine obviously. After doing make uninstall and make install, running freshclam says that I am still running 0.94-exp, not 0.94. Running freshclam from the source dir says the same thing: Did you configure with --enable-experimental? Yes, I used --enable-experimental ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] ClamAV 0.94 Webinar Reminder
Hi Everyone, My apologies for sending this again if you've already read this. It's a reminder for those who may have missed it last week. The next ClamAV users webcast will be tomorrow at 1700GMT (1800BST; 1900CEST; 1300EDT). The presentation, given by Török Edwin, will cover the new features of ClamAV 0.94, such as logical signatures and unit testing, and also its improvements in areas such as anti-phishing and script scanning. This will be followed by an overview of the evolution of anti-phishing and script malware detection technology in ClamAV from 0.93 to 0.94, and by a live demonstration of how to use some of the new and improved features in 0.94. Registration Details for the live session: Date: Wed 3rd September Time: 1700GMT Registration link: https://sourcefire.webex.com/sourcefire/onstage/g.php?d=799008644t=a As always this session will be recorded and archived on ClamAV.net and Sourcefire.com. I hope you can join us. Regards, Nigel -- Nigel Horne, [EMAIL PROTECTED] Director of Product Management (ClamAV), Sourcefire, http://www.sourcefire.com +44 1226 241048 or +1 706 705 4022 FAX: +44 870 705 9334, Skype: nigelhorne Come to Las Vegas to see the latest in Sourcefire and open source innovation. Register at www.bossconference.com by September 30th to save $200! ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
-Original Message- From: [EMAIL PROTECTED] [mailto:clamav-users- [EMAIL PROTECTED] On Behalf Of Brandon Perry Sent: Tuesday, September 02, 2008 12:06 PM To: ClamAV users ML Subject: [Clamav-users] ClamAV 0.94 release Configuring on CentOS 5.2 x64 produces the following warnings: # ./configure --prefix=/usr --sysconfdir=/etc --enable-experimental \ --enable-milter checking for CHECK... no configure: WARNING: unable to find 'check' using pkg-config: No package 'check' found and checking for libgmp... no configure: WARNING: ** GNU MP 2 or newer NOT FOUND - digital signature support will be disabled ! however, # yum provides check check-devel.x86_64 : Libraries and headers for developing programs with check check-devel.i386 : Libraries and headers for developing programs with check # yum install check-devel Package check-devel - 0.9.3-5.fc6.i386 is already installed. Package check-devel - 0.9.3-5.fc6.x86_64 is already installed. # yum install gmp-devel Package gmp-devel - 4.1.4-10.el5.i386 is already installed. Package gmp-devel - 4.1.4-10.el5.x86_64 is already installed. Additionally, configure seems to find libgmp when option --prefix=/usr is not used. # ./configure |grep gmp checking for libgmp... yes # ./configure --prefix=/usr |grep gmp checking for libgmp... no What's the deal with the new requirement for 'check' and why would option --prefix=/usr break the ability to find libgmp? Jason A. Bertoch Network Administrator [EMAIL PROTECTED] Electronet Broadband Communications 3411 Capital Medical Blvd. Tallahassee, FL 32308 (V) 850.222.0229 (F) 850.222.8771 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
You need to check to run 'make check' as per above. On Tue, Sep 2, 2008 at 1:44 PM, Jason Bertoch [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:clamav-users- [EMAIL PROTECTED] On Behalf Of Brandon Perry Sent: Tuesday, September 02, 2008 12:06 PM To: ClamAV users ML Subject: [Clamav-users] ClamAV 0.94 release Configuring on CentOS 5.2 x64 produces the following warnings: # ./configure --prefix=/usr --sysconfdir=/etc --enable-experimental \ --enable-milter checking for CHECK... no configure: WARNING: unable to find 'check' using pkg-config: No package 'check' found and checking for libgmp... no configure: WARNING: ** GNU MP 2 or newer NOT FOUND - digital signature support will be disabled ! however, # yum provides check check-devel.x86_64 : Libraries and headers for developing programs with check check-devel.i386 : Libraries and headers for developing programs with check # yum install check-devel Package check-devel - 0.9.3-5.fc6.i386 is already installed. Package check-devel - 0.9.3-5.fc6.x86_64 is already installed. # yum install gmp-devel Package gmp-devel - 4.1.4-10.el5.i386 is already installed. Package gmp-devel - 4.1.4-10.el5.x86_64 is already installed. Additionally, configure seems to find libgmp when option --prefix=/usr is not used. # ./configure |grep gmp checking for libgmp... yes # ./configure --prefix=/usr |grep gmp checking for libgmp... no What's the deal with the new requirement for 'check' and why would option --prefix=/usr break the ability to find libgmp? Jason A. Bertoch Network Administrator [EMAIL PROTECTED] Electronet Broadband Communications 3411 Capital Medical Blvd. Tallahassee, FL 32308 (V) 850.222.0229 (F) 850.222.8771 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 release
On 2008-09-02 21:44, Jason Bertoch wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:clamav-users- [EMAIL PROTECTED] On Behalf Of Brandon Perry Sent: Tuesday, September 02, 2008 12:06 PM To: ClamAV users ML Subject: [Clamav-users] ClamAV 0.94 release Configuring on CentOS 5.2 x64 produces the following warnings: # ./configure --prefix=/usr --sysconfdir=/etc --enable-experimental \ --enable-milter checking for CHECK... no configure: WARNING: unable to find 'check' using pkg-config: No package 'check' found and checking for libgmp... no configure: WARNING: ** GNU MP 2 or newer NOT FOUND - digital signature support will be disabled ! however, # yum provides check check-devel.x86_64 : Libraries and headers for developing programs with check check-devel.i386 : Libraries and headers for developing programs with check Don't worry about the pkg-config warning, does it say 'checking linking with check ... ok'? Does 'make check' work? You can read more about 'make check' here: http://www.clamav.net/doc/latest/html/node15.html And what to do if it fails here: http://www.clamav.net/doc/latest/html/node16.html 'make check' has been part of 0.94rc1, so you should already know this ;) Additionally, configure seems to find libgmp when option --prefix=/usr is not used. # ./configure |grep gmp checking for libgmp... yes # ./configure --prefix=/usr |grep gmp checking for libgmp... no Is your libgmp in /usr/lib, or /usr/local/lib? What's the deal with the new requirement for 'check' and why would option --prefix=/usr break the ability to find libgmp? Check is optional, its only needed for 'make check', 'make' and 'make install' work fine without it. As for libgmp I don't remember any changes since 0.93.3 in that area. If you can't get it to work, open a bugreport and attach your config.log. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] ClamAV 0.94 build problem on Cygwin
Hi, Something changed in configure which results on a wrong setting for the existence of gethostbyname_r, it worked fine on 0.94rc1, now it doesn't build unless using the following. Simple solution: add '--disable-gethostbyname_r' to configure line. I haven't found what changed and how the result for the test is coming out wrong, for reference here is the configure output line for both versions: 0.94rc1 --- checking for gethostbyname_r... support disabled 0.94 checking for gethostbyname_r... yes, and it takes 5 arguments ... (and the failure) clamav-0.94/libclamav/mbox.c:4537: undefined reference to `_gethostbyname_r' Creating library file: .libs/libclamav.dll.a No problem building with the proposed workaround, except 'make check' which needs removing the socket before testing, as in lines 25 and 39 of check_clamd.sh: rm -f clamdscan.log clamd-test.socket But then testing passing a file descriptor fails... I don't think Cygwin has that functionality, can't pass file descriptors around. Hope this is useful. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
IIRC, the announcement said that POSIX breakage would happen if you tried to compile 0.94 on cygwin... On Tue, Sep 2, 2008 at 4:16 PM, René Berber [EMAIL PROTECTED] wrote: Hi, Something changed in configure which results on a wrong setting for the existence of gethostbyname_r, it worked fine on 0.94rc1, now it doesn't build unless using the following. Simple solution: add '--disable-gethostbyname_r' to configure line. I haven't found what changed and how the result for the test is coming out wrong, for reference here is the configure output line for both versions: 0.94rc1 --- checking for gethostbyname_r... support disabled 0.94 checking for gethostbyname_r... yes, and it takes 5 arguments ... (and the failure) clamav-0.94/libclamav/mbox.c:4537: undefined reference to `_gethostbyname_r' Creating library file: .libs/libclamav.dll.a No problem building with the proposed workaround, except 'make check' which needs removing the socket before testing, as in lines 25 and 39 of check_clamd.sh: rm -f clamdscan.log clamd-test.socket But then testing passing a file descriptor fails... I don't think Cygwin has that functionality, can't pass file descriptors around. Hope this is useful. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
From the announcement: ** This version drops the special support for Cygwin. Our QA process showed ** serious problems with ClamAV builds under Cygwin due to some low-level ** incompatibilities in the POSIX compatibility layer, resulting in unreliable ** ClamAV behaviour. On Tue, Sep 2, 2008 at 4:22 PM, Brandon Perry [EMAIL PROTECTED]wrote: IIRC, the announcement said that POSIX breakage would happen if you tried to compile 0.94 on cygwin... On Tue, Sep 2, 2008 at 4:16 PM, René Berber [EMAIL PROTECTED]wrote: Hi, Something changed in configure which results on a wrong setting for the existence of gethostbyname_r, it worked fine on 0.94rc1, now it doesn't build unless using the following. Simple solution: add '--disable-gethostbyname_r' to configure line. I haven't found what changed and how the result for the test is coming out wrong, for reference here is the configure output line for both versions: 0.94rc1 --- checking for gethostbyname_r... support disabled 0.94 checking for gethostbyname_r... yes, and it takes 5 arguments ... (and the failure) clamav-0.94/libclamav/mbox.c:4537: undefined reference to `_gethostbyname_r' Creating library file: .libs/libclamav.dll.a No problem building with the proposed workaround, except 'make check' which needs removing the socket before testing, as in lines 25 and 39 of check_clamd.sh: rm -f clamdscan.log clamd-test.socket But then testing passing a file descriptor fails... I don't think Cygwin has that functionality, can't pass file descriptors around. Hope this is useful. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml -- http://www.volatileminds.net -- http://www.volatileminds.net ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Brandon Perry wrote: IIRC, the announcement said that POSIX breakage would happen if you tried to compile 0.94 on cygwin... If you mean this part : ** This version drops the special support for Cygwin. Our QA process showed ** serious problems with ClamAV builds under Cygwin due to some low-level ** incompatibilities in the POSIX compatibility layer, resulting in unreliable ** ClamAV behaviour. It sounds like non-sense to me, version 0.94rc1 works fine, and both versions build fine. The above statement seems to come from somebody that didn't even test, didn't look at what 'make check' was doing, and didn't really care. serious problems ? Only problem is the test I mentioned, passing a file descriptor is not supported under Cygwin as far as I know. unreliable behaviour ? Does that mean the distribution/use of older bzip2 libraries? The warning at configure time is clear, I'm not sure it is correct, the CVE says before 1.0.5, Cygwin uses 1.0.5 . And the gem: incompatibilties in ... compatibility layer; it is or it isn't compatible? The Cygwin folks make an effort for being POSIX compatible. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
René Berber wrote: serious problems ? Only problem is the test I mentioned, passing a file descriptor is not supported under Cygwin as far as I know. I have no cygwin experience, but Windows *does* allow passing file descriptors to child process. Not in the same way as unix, but I'd find odd the cygwin guys didn't manage to adapt that, given that they were able to do much more complex things, such as emulating fork() ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Cygwin
Sarocet wrote: René Berber wrote: serious problems ? Only problem is the test I mentioned, passing a file descriptor is not supported under Cygwin as far as I know. I have no cygwin experience, but Windows *does* allow passing file descriptors to child process. Not in the same way as unix, but I'd find odd the cygwin guys didn't manage to adapt that, given that they were able to do much more complex things, such as emulating fork() My reference is old, so things could have changed. http://sourceware.org/ml/cygwin/2005-10/msg00672.html I have no first hand experience using fd passing, the problem could be more specific to passing stdin's fd, which is what the test script does. -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] ClamAV 0.94 build problem on Solaris 9
Hello,
Sorry for the long post.
The following command and error stops clamav build, any ideas?
gcc -shared -Wl,-h -Wl,libclamav.so.5 -o .libs/libclamav.so.5.0.1
.libs/matcher-ac.o .libs/matcher-bm.o .libs/matcher.o .libs/md5.o
.libs/others.o .libs/readdb.o .libs/cvd.o .libs/dsig.o .libs/str.o
.libs/scanners.o .libs/textdet.o .libs/filetypes.o .libs/rtf.o
.libs/blob.o .libs/mbox.o .libs/message.o .libs/table.o .libs/text.o
.libs/ole2_extract.o .libs/vba_extract.o .libs/msexpand.o .libs/pe.o
.libs/disasm.o .libs/upx.o .libs/htmlnorm.o .libs/chmunpack.o
.libs/rebuildpe.o .libs/petite.o .libs/wwunpack.o .libs/unsp.o
.libs/aspack.o .libs/packlibs.o .libs/fsg.o .libs/mew.o .libs/upack.o
.libs/line.o .libs/untar.o .libs/unzip.o .libs/inflate64.o
.libs/special.o .libs/binhex.o .libs/is_tar.o .libs/tnef.o
.libs/autoit.o .libs/strlcpy.o .libs/regcomp.o .libs/regerror.o
.libs/regexec.o .libs/regfree.o .libs/unarj.o .libs/bzlib.o
.libs/nulsft.o .libs/infblock.o .libs/pdf.o .libs/spin.o .libs/yc.o
.libs/elf.o .libs/sis.o .libs/uuencode.o .libs/phishcheck.o
.libs/phish_domaincheck_db.o .libs/phish_whitelist.o .libs/regex_list.o
.libs/regex_suffix.o .libs/mspack.o .libs/cab.o .libs/entconv.o
.libs/hashtab.o .libs/dconf.o .libs/lzma_iface.o .libs/explode.o
.libs/textnorm.o .libs/dlp.o .libs/js-norm.o .libs/uniq.o
.libs/version.o -Wl,-z -Wl,allextract lzma/.libs/liblzma.a -Wl,-z
-Wl,defaultextract
-R/usr/share/src/clamav-0.94/libclamunrar_iface/.libs -R/usr/local/lib
-R/usr/local/lib ../libclamunrar_iface/.libs/libclamunrar_iface.so
-L/usr/share/src/clamav-0.94/libclamunrar/.libs -L/usr/local/lib -lz
-lbz2 /usr/local/lib/libgmp.so /usr/local/lib/libiconv.so -L/usr/lib
-L/usr/openwin/lib -L/usr/local/ssl/lib -L/usr/local/BerkeleyDB.4.2/lib
-lpthread -lnsl -lsocket -lc -Wl,-M -Wl,../libclamav/libclamav.map
ld: fatal: ../libclamav/libclamav.map: 109: symbol `uniq_get' is already
defined in file: ../libclamav/libclamav.map
The file libclamav.map does indeed have uniq_get twice, I can't find
where the duplicate comes from, it's not duplicated on clamav's code.
Here's the contents of the map:
CLAMAV_PUBLIC {
global:
cl_build;
cl_cvdfree;
cl_cvdhead;
cl_cvdparse;
cl_cvdverify;
cl_debug;
cl_dup;
cl_free;
cl_load;
cl_loaddb;
cl_loaddbdir;
cl_retdbdir;
cl_retflevel;
cl_retver;
cl_scandesc;
cl_scanfile;
cl_settempdir;
cl_statchkdir;
cl_statfree;
cl_statinidir;
cl_strerror;
local:
*;
};
CLAMAV_PRIVATE {
global:
cli_ac_setdepth;
cli_strtok;
cli_untgz;
cli_regcomp;
cli_regexec;
cli_regfree;
cli_strrcpy;
cli_strbcasestr;
cli_isnumber;
cli_gentemp;
cli_gentempfd;
cli_rmdirs;
cli_chomp;
cli_rndnum;
cli_decodesig;
cli_calloc;
cli_ole2_extract;
cli_errmsg;
cli_debug_flag;
cli_dbgmsg_internal;
cli_vba_readdir;
cli_vba_inflate;
cli_ppt_vba_read;
cli_wm_readdir;
cli_wm_decrypt_macro;
cli_readn;
cli_str2hex;
cli_md5file;
cli_md5stream;
html_normalise_fd;
cli_utf16toascii;
cli_malloc;
cli_memstr;
cli_strdup;
cli_realloc;
cli_ctime;
tableCreate;
tableDestroy;
tableRemove;
tableFind;
tableIterate;
tableUpdate;
tableInsert;
cli_warnmsg;
cli_strtokbuf;
cli_leavetemps_flag;
uniq_get; ---
cli_js_init;
cli_js_process_buffer;
cli_js_parse_done;
cli_js_destroy;
cli_js_output;
cli_unescape;
cli_textbuffer_append_normalize;
cli_dconf_init;
cli_regex2suffix;
html_normalise_mem;
init_regex_list;
is_regex_ok;
regex_list_done;
regex_list_add_pattern;
cli_build_regex_list;
regex_list_match;
cli_initengine;
phishing_init;
init_domainlist;
init_whitelist;
phishing_done;
blobCreate;
blobAddData;
phishingScan;
blobDestroy;
load_regex_matcher;
html_tag_arg_free;
disasmbuf;
uniq_init;
uniq_free;
uniq_add;
uniq_get; ---
cli_hex2str;
cli_ac_init;
cli_ac_initdata;
cli_ac_buildtrie;
cli_ac_scanbuff;
cli_ac_freedata;
cli_ac_free;
cli_parse_add;
cli_bm_init;
cli_bm_scanbuff;
cli_bm_free;
local:
*;
};
I did not test 0.94rc1 on this system.
--
René Berber
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Re: [Clamav-users] ClamAV 0.94 build problem on Solaris 9
Additional info: gcc is version 3.4.6, ld in not GNU ld, it is Sun's version 5.9-1.378 . In fact, ld's -M parameter seems to have different meaning, and it also could be a bug (ld itself added the symbol twice). -- René Berber ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
