> The Windows binary is getting old. I believe its a
> development version
> prior to .66. I'd like to get a .67-1 (or later) version.
>
> I've got Cygwin installed on one of my computers. Can I
> build it myself?
> If so, is there a how-to or an old mailing list message with
> instructions?
Ju
I compiled the clamd.exe from current cvs - under cygwin.
It loads and works OK with these files:
main.cvd 1037239 bytes
daily.cvd 72297 bytes
But now freshclam downloaded the new (?) version of these files:
ClamAV update process started at Sat Feb 28 23:32:57 2004
Reading CVD header (main.cvd):
clamd+clamDscan under Windows 2003 PIII/1GHz
--- SCAN SUMMARY ---
Infected files: 7611
Time: 478.706 sec (7 m 58 s)
---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux wit
I'm recompiled clamav under cygwin with GNU MP enabled (static)
to support digital signatures.
clamd:
LibClamAV debug: ./share/clamav/daily.cvd: CVD file detected
LibClamAV debug: in cli_cvdload()
LibClamAV debug: MD5(.tar.gz) = fdb603f18c089ba34fef74c8a87bec85
LibClamAV debug: Decoded signature:
> I found, this problem in the clamscan.exe itself.
It not read clamav.conf and not autodetects many mailbox
formats. But works fine when options set in command line.
> Is it modified source code or do you compile it in a special way?
Below are changes made in 'configure' script to allow
using cl
> > The same problem with the
> > clamscan.exe 383090 17.02.04 06:18
> > from http://clamav.or.id/snapshot/clamav-devel-latest.cygwin.zip
> > it not detects MyDoom (Worm.SCO.A), Sircam and some others viruses.
> > On the WinXP PC with Cygwin installed.
I found, this problem in the clamscan.exe
> The same problem with the
> clamscan.exe 383090 17.02.04 06:18
> from http://clamav.or.id/snapshot/clamav-devel-latest.cygwin.zip
> it not detects MyDoom (Worm.SCO.A), Sircam and some others viruses.
> On the WinXP PC with Cygwin installed.
>
> Looks strange. I will test it on other PC (Win20
> >From: Fajar A. Nugraha <[EMAIL PROTECTED]>
>
> > It seems Nigel already fixed that
> > Which means starting from devel-20040215 the daily build
> should work
> > fine too.
>
> But clamav-devel-latest.cygwin.zip from 02/16/04 - didn't work fine :(
> Will download more current version now...
The
>From: Fajar A. Nugraha <[EMAIL PROTECTED]>
> It seems Nigel already fixed that
> Which means starting from devel-20040215 the daily build should work
> fine too.
But clamav-devel-latest.cygwin.zip from 02/16/04 - didn't work fine :(
Will download more current version now...
> >The fixed version
> Date: Mon, 16 Feb 2004 16:15:58 +0700
> From: "Fajar A. Nugraha" <[EMAIL PROTECTED]>
> Subject: Re: [Clamav-users] Re: clamav-devel 20040213 for windows
> Just as I thought. ANyway, the developers seems to have fixed this by
> adding O_BINARY (again) for Cygwin build only.
> As usual, you can ge
Nigel,
Diff for /clamav/clamav-devel/libclamav/mbox.c between version 1.40 and
1.41:
http://cvs.sourceforge.net/viewcvs.py/clamav/clamav-devel/libclamav/mbox.c?r
1=1.40&r2=1.41
You deleted O_BINARY in v1.41 again?!
This is origin of problems with cygwin version, compiled by Brian Bruns.
Please fix
> From: "Brian Bruns" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Date: Fri, 13 Feb 2004 23:41:59 -0500
> Subject: [Clamav-users] clamav-devel 20040213 for windows
> Reply-To: [EMAIL PROTECTED]
>
> Ok, I finished it up quickly and uploaded, so enjoy.
>
> http://www.sosdg.org/clamav-win32/clamav
> ClamAV-0.66 and ClamAV-devel, the last hunk of the patch failed, so
> see the attached patch instead. I've tested it on Linux, but would
> like to know if it works on Windows. According to MS library docs
> it ought to work, but I'm not sure about the Cygwin runtime library.
> Maybe you could t
> Great !
>
> Could anybody briefly explain wich parts of Cygwin are
> necessary to build
> Clamav under Win32 ? I have some knowledge of C but don't have any
> experience in Cygwin tools. Is the C compiler the only needed tool to
> compiler Clamav ?
Compilation under cygwin is the same as in unix
> read(stream) and write(stream) under Cygwin work as text
> functions instead of binary ones - expand LF to CRLF ?
> How to override this?
I've added "|O_BINARY" to freshclam/manager.c[472]:
if((fd = open(file, O_WRONLY|O_CREAT|O_EXCL|O_BINARY, 0644)) == -1) {
and now freshclam.exe works rig
> Do not know, why this happens (13 :). Just commented out
> this "if (bread" fragment, recompiled, and now this works
> for all tested Worm.SCO.A infected files on this PC.
When I added "|O_BINARY" to this code in mbox.c this 13/14
magic_buffer problem also fix.
#else
(void)mktemp(filena
Compare files "original\main.cvd" and
"downloaded_by_freshclam_under_cygwin\MAIN.CVD"
071D: 0A 0D
071E: 2F 0A
071F: DD 2F
0720: 6D DD
0721: FB 6D
0722: DB FB
0723: 4E DB
0724: 87 4E
0x0D 0x0A - line terminator in DOS/Windows/Cygwin...
Seems, the problem is same as
Nigel,
I found difference in these 2 cases.
On the second PC (WinXP with installed Cygwin) this code
bread = read(desc, magic, MAGIC_BUFFER_SIZE);
returns bread=13 instead of 14 (#define MAGIC_BUFFER_SIZE 14)
and later failed to pass this check:
if (bread != MAGIC_BUFFER_SIZE) {
Dear Nigel,
Here is 2 debug logs from clamd from 2 different PC.
1st - Windows 2003 Server w/o Cygwin installed:
...
LibClamAV debug: messageFindArgument: compare 8 bytes of filename with
filename="text.zip"
LibClamAV debug: blobSetFilename: text.zip
LibClamAV debug: Mixed message part 2 is of ty
> > Please check that you have the latest source code, in
> particular my message.c is
> > 1.29, and my mbox.c is 1.39
>
> From CVS\Entries in the sources I compiled:
> /message.c/1.29/Tue Feb 10 17:01:30 2004//
> /mbox.c/1.39/Fri Feb 6 13:46:08 2004//
Very like some Cygwin issues... I've copied
> I just tried sending you some e-mail but got this message.
> Please fix your system and when you've done so let me know
> and I'll try chatting again.
>
> -Nigel
> (reason: 550 Your message is classified as SPAM! If this
> an error, please click here:
> http://eserv.ru/MailClassify/[EMAIL PRO
21 matches
Mail list logo
