Re: [Clamav-devel] clamav-0.96 is this properly working???
On 2010-04-19 18:02, Dale Walsh wrote: > Once all done and working I saw no need to keep the hacked files and > just backed up the binaries. OK, nevermind. > I'll send you a link to the binaries if you want to look at them. No need to do that. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 08:42 AM, Török Edwin wrote: On 2010-04-19 15:40, Dale Walsh wrote: On Apr 19, 2010, at 07:05 AM, Török Edwin wrote: On 2010-04-19 12:44, Dale Walsh wrote: I submitted the clamd stderr information as requested,, is there anything else you need? I tested on a Mac OS X 10.5.8 ppc, with gcc 4.0.1 and all testfiles (except RAR) were detected in a static build. Tested 10.4.0 - 10.4.11 ppc, built with gcc 4.0 using a modified build process and all testfiles including rar now pass. The only problem is that clam.mail is missed, right? (well quite a big problem if you're scanning mail). Fixed some of the incompatible pointer type warnings and mail now works. When you have some time can you post a patch with the modifications you made? A patch??? the only patch I have is the ppcpatch.txt file that you already know about. It involved configuring as static no shared, saving the Makefile's, configuring as static no shared, merging the the two to get the binaries to build as I needed and fixing the warnings as I went along. First built libltdl then libclamav, edited libclamav.la to remove the dlopen and add the libclamunrar.la as a dependancy for the remainder of the build but restored for the install process so I could get a static build with a dynamic module using DESTDIR to control the intermediate install to move files around. Once all done and working I saw no need to keep the hacked files and just backed up the binaries. What version of Mac OS X do you have (sw_vers will tell you), what version of gcc (gcc -v will tell you)? Configured with gcc 3.3 but built with gcc 4.0. Maybe thats why it failed. It wouldn't work using 3.3 (compiler too old) and wouldn't compile if configured with gcc 4.0 so I configured with gcc 3.3 then switched compiler to 4.0 to build. And could you post the output from clamd's stderr when you run clamdscan test/clam.mail? (I assume it is missed in this case too) No longer missed. OK, glad to hear. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net I'll send you a link to the binaries if you want to look at them. -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] The upcoming 15 April kill-switch (and a feature suggestion)
On some rpm linux, eg RH5 for example, there is yum. You can provide them a private yum server and this will done. On FreeBSD, there is packages, same add a correct line into /etc/make.conf and portupgrade -pP will fix this for you. How about you do us all a favor and cut out the patronizing? Everyone involved in this discussion knows how automated package upgrades work. This is not the point... 6 months for a security software is big. Do you forgot to upgrade your IOS or Firewall software ? The IOS and Firewall vendors provide safe, minimal upgrade paths to address security concerns. They support software releases for years. See, for example, the Symantec policy I referenced earlier in this discussion, which indicates that Symantec supports any software it releases for SEVEN YEARS after the next major version is released. The ClamAV team cannot justify putting themselves in the same vote as "your IOS or Firewall software" unless they're willing to make the same kind of support commitment. But they don't. They put out new releases at least once per year and usually more than that, each new release contains substantial new functionality (and usually substantial new bugs to go along with it), and they don't issue security patches for old releases once new ones come out. Clamav is security software, Yes, it is, which is why it's all the more important for its authors and maintainers to provide reasonable upgrade paths to address security concerns for people and organizations who are not prepared to take the latest and greatest stuff within months after it is released. Make no mistake, I think ClamAV is a nice package, I'm glad it exists, I'm grateful to the people who have put time and effort into creating, maintaining and enhancing it, and my company will continue to use it as part of our product's open-source platform. However, all of these things being true does not change the fact that I agree with David Skoll that the ClamAV maintainers sometimes show little regard for the real-world consumers of the package. The plain, simple fact is that there are other ways this could and should have been handled. Jik ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On 2010-04-19 15:40, Dale Walsh wrote: > > On Apr 19, 2010, at 07:05 AM, Török Edwin wrote: > >> On 2010-04-19 12:44, Dale Walsh wrote: >>> >>> I submitted the clamd stderr information as requested,, is there >>> anything else you need? >> >> I tested on a Mac OS X 10.5.8 ppc, with gcc 4.0.1 and all testfiles >> (except RAR) were detected in a static build. > > Tested 10.4.0 - 10.4.11 ppc, built with gcc 4.0 using a modified build > process and all testfiles including rar now pass. > >> The only problem is that clam.mail is missed, right? (well quite a big >> problem if you're scanning mail). > > Fixed some of the incompatible pointer type warnings and mail now works. When you have some time can you post a patch with the modifications you made? > >> What version of Mac OS X do you have (sw_vers will tell you), what >> version of gcc (gcc -v will tell you)? > > Configured with gcc 3.3 but built with gcc 4.0. Maybe thats why it failed. > >> And could you post the output from clamd's stderr when you run >> clamdscan test/clam.mail? (I assume it is missed in this case too) > > No longer missed. OK, glad to hear. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 07:05 AM, Török Edwin wrote: On 2010-04-19 12:44, Dale Walsh wrote: I submitted the clamd stderr information as requested,, is there anything else you need? I tested on a Mac OS X 10.5.8 ppc, with gcc 4.0.1 and all testfiles (except RAR) were detected in a static build. Tested 10.4.0 - 10.4.11 ppc, built with gcc 4.0 using a modified build process and all testfiles including rar now pass. The only problem is that clam.mail is missed, right? (well quite a big problem if you're scanning mail). Fixed some of the incompatible pointer type warnings and mail now works. What version of Mac OS X do you have (sw_vers will tell you), what version of gcc (gcc -v will tell you)? Configured with gcc 3.3 but built with gcc 4.0. And could you post the output from clamd's stderr when you run clamdscan test/clam.mail? (I assume it is missed in this case too) No longer missed. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On 2010-04-19 12:44, Dale Walsh wrote: > > I submitted the clamd stderr information as requested,, is there > anything else you need? I tested on a Mac OS X 10.5.8 ppc, with gcc 4.0.1 and all testfiles (except RAR) were detected in a static build. The only problem is that clam.mail is missed, right? (well quite a big problem if you're scanning mail). What version of Mac OS X do you have (sw_vers will tell you), what version of gcc (gcc -v will tell you)? And could you post the output from clamd's stderr when you run clamdscan test/clam.mail? (I assume it is missed in this case too) Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On 2010-04-19 12:44, Dale Walsh wrote: > > On Apr 19, 2010, at 05:11 AM, Török Edwin wrote: > >> You can remove daily.cvd/cld, and stop freshclam as temporary solution >> to get 0.92 working, until you get 0.95.3, or 0.96 working. >> >> Best regards, >> --Edwin >> ___ >> http://lurker.clamav.net/list/clamav-devel.html >> Please submit your patches to our Bugzilla: http://bugs.clamav.net >> > > > I built everything as static so including the dynamic (shared) > libclamav.dylib library is not required for clamd however > libclamunrar.dylib is linked in the libclamunrar_iface module so it has > been installed. > > The code looks like it expects to load the libclamunrar_iface module > from disk and doesn't check to see if it's embedded (static linked). > > I submitted the clamd stderr information as requested,, is there > anything else you need? Thanks, I'll let you know if I need additional information. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 05:11 AM, Török Edwin wrote: You can remove daily.cvd/cld, and stop freshclam as temporary solution to get 0.92 working, until you get 0.95.3, or 0.96 working. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net I built everything as static so including the dynamic (shared) libclamav.dylib library is not required for clamd however libclamunrar.dylib is linked in the libclamunrar_iface module so it has been installed. The code looks like it expects to load the libclamunrar_iface module from disk and doesn't check to see if it's embedded (static linked). I submitted the clamd stderr information as requested,, is there anything else you need? -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 05:11 AM, Török Edwin wrote: On 04/19/2010 12:06 PM, Dale Walsh wrote: On Apr 19, 2010, at 03:27 AM, Török Edwin wrote: On 04/19/2010 09:21 AM, Dale Walsh wrote: Foreground = "yes" Debug = "yes" Since you have Foreground+Debug active please redirect the stderr output of clamd to a file. Then scan the files in test/ Then open a bugreport on bugs.clamav.net, and attach the stderr output (not the syslog output, since the debug info is not sent to syslog). Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net I've submitted additional information and I certainly hope you weren't expecting my continued participation on the bug site. You didn't provide the stderr output from clamd, that is needed to debug this problem further. I'll submit this information since you need it. I think this is merely a configuration issue, since noone else has reported that 0.95/0.96 is missing those test files on Mac OS X. The only reason I registered to submit the information was that it might be useful in helping you track down the issue(s) but I don't have the time to pursue this any further than providing you with this information, my time is better spent finding an acceptable solution for a production environment because you ensured that the working 0.92 solution I was using is no longer able to operate when you made the minimum requirement 0.95. You can remove daily.cvd/cld, and stop freshclam as temporary solution to get 0.92 working, until you get 0.95.3, or 0.96 working. I'll recompile without the FD passing support and rebuild to get the loadable module since it is unclear what benefit this really has. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On 04/19/2010 12:06 PM, Dale Walsh wrote: > > On Apr 19, 2010, at 03:27 AM, Török Edwin wrote: > >> On 04/19/2010 09:21 AM, Dale Walsh wrote: >>> Foreground = "yes" >>> Debug = "yes" >> >> Since you have Foreground+Debug active please redirect the stderr output >> of clamd to a file. >> Then scan the files in test/ >> >> Then open a bugreport on bugs.clamav.net, and attach the stderr output >> (not the syslog output, since the debug info is not sent to syslog). >> >> Best regards, >> --Edwin >> ___ >> http://lurker.clamav.net/list/clamav-devel.html >> Please submit your patches to our Bugzilla: http://bugs.clamav.net >> > > I've submitted additional information and I certainly hope you weren't > expecting my continued participation on the bug site. You didn't provide the stderr output from clamd, that is needed to debug this problem further. I think this is merely a configuration issue, since noone else has reported that 0.95/0.96 is missing those test files on Mac OS X. > > The only reason I registered to submit the information was that it might > be useful in helping you track down the issue(s) but I don't have the > time to pursue this any further than providing you with this > information, my time is better spent finding an acceptable solution for > a production environment because you ensured that the working 0.92 > solution I was using is no longer able to operate when you made the > minimum requirement 0.95. You can remove daily.cvd/cld, and stop freshclam as temporary solution to get 0.92 working, until you get 0.95.3, or 0.96 working. Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 03:27 AM, Török Edwin wrote: On 04/19/2010 09:21 AM, Dale Walsh wrote: Foreground = "yes" Debug = "yes" Since you have Foreground+Debug active please redirect the stderr output of clamd to a file. Then scan the files in test/ Then open a bugreport on bugs.clamav.net, and attach the stderr output (not the syslog output, since the debug info is not sent to syslog). Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net I've submitted additional information and I certainly hope you weren't expecting my continued participation on the bug site. The only reason I registered to submit the information was that it might be useful in helping you track down the issue(s) but I don't have the time to pursue this any further than providing you with this information, my time is better spent finding an acceptable solution for a production environment because you ensured that the working 0.92 solution I was using is no longer able to operate when you made the minimum requirement 0.95. -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On Apr 19, 2010, at 03:27 AM, Török Edwin wrote: On 04/19/2010 09:21 AM, Dale Walsh wrote: Foreground = "yes" Debug = "yes" Since you have Foreground+Debug active please redirect the stderr output of clamd to a file. Then scan the files in test/ Then open a bugreport on bugs.clamav.net, and attach the stderr output (not the syslog output, since the debug info is not sent to syslog). Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net Filed as you requested and I hope this is sufficient information to help you do whatever you need to do to fix it. https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1976 I take it there is an issue (excluding the faulty rar code) based on the results of the test run. This leave me with a couple of options, reduce clamav functionality down to the level of the 0.92 version so that it can at least perform some kind of protection or use something else (not my first choice). -- Dale PGP.sig Description: This is a digitally signed message part ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: [Clamav-devel] clamav-0.96 is this properly working???
On 04/19/2010 09:21 AM, Dale Walsh wrote: > Foreground = "yes" > Debug = "yes" Since you have Foreground+Debug active please redirect the stderr output of clamd to a file. Then scan the files in test/ Then open a bugreport on bugs.clamav.net, and attach the stderr output (not the syslog output, since the debug info is not sent to syslog). Best regards, --Edwin ___ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
