Re: [jes...@cisco.com: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate]
From: The Doctor via freebsd-ports Subject: [jes...@cisco.com: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate] Date: Tue, 18 Aug 2020 16:35:28 -0600 > heads up! Folloing is patch to update security/clamav to 0.103.0-rc. Please keep in mind that 0.103.0 is still release candidate and not suitable for production use. Index: security/clamav/Makefile === --- security/clamav/Makefile(revision 545179) +++ security/clamav/Makefile(working copy) @@ -1,7 +1,7 @@ # $FreeBSD$ PORTNAME= clamav -PORTVERSION= 0.102.4 +DISTVERSION= 0.103.0-rc PORTEPOCH= 1 CATEGORIES=security MASTER_SITES= https://www.clamav.net/downloads/production/ Index: security/clamav/distinfo === --- security/clamav/distinfo(revision 545179) +++ security/clamav/distinfo(working copy) @@ -1,3 +1,3 @@ -TIMESTAMP = 1594929106 -SHA256 (clamav-0.102.4.tar.gz) = eebd426a68020ecad0d2084b8c763e6898ccfd5febcae833d719640bb3ff391b -SIZE (clamav-0.102.4.tar.gz) = 1323 +TIMESTAMP = 1597791094 +SHA256 (clamav-0.103.0-rc.tar.gz) = bf3d77969bd5dbf7dd4eb820a3812788fd6cab7aaf8bed3c8facea909917 +SIZE (clamav-0.103.0-rc.tar.gz) = 13398760 Index: security/clamav/pkg-plist === --- security/clamav/pkg-plist (revision 545179) +++ security/clamav/pkg-plist (working copy) @@ -36,10 +36,10 @@ %%PORTDOCSDOCSDIR%%/html/UserManual/libclamav.html %%UNRAR%%lib/libclamunrar.so %%UNRAR%%lib/libclamunrar.so.9 -%%UNRAR%%lib/libclamunrar.so.9.0.4 +%%UNRAR%%lib/libclamunrar.so.9.0.5 %%UNRAR%%lib/libclamunrar_iface.so %%UNRAR%%lib/libclamunrar_iface.so.9 -%%UNRAR%%lib/libclamunrar_iface.so.9.0.4 +%%UNRAR%%lib/libclamunrar_iface.so.9.0.5 @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%DBDIR%% @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%LOGDIR%% @dir(%%CLAMAVUSER%%,%%CLAMAVGROUP%%,0755) %%RUNDIR%% @@ -60,10 +60,10 @@ include/libfreshclam.h lib/libclamav.so lib/libclamav.so.9 -lib/libclamav.so.9.0.4 +lib/libclamav.so.9.0.5 lib/libfreshclam.so lib/libfreshclam.so.2 -lib/libfreshclam.so.2.0.0 +lib/libfreshclam.so.2.0.1 libdata/pkgconfig/libclamav.pc man/man1/clambc.1.gz man/man1/clamconf.1.gz --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[jes...@cisco.com: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate]
heads up! - Forwarded message from "Joel Esler (jesler)" - Date: Tue, 18 Aug 2020 21:57:23 + From: "Joel Esler (jesler)" To: ClamAV users ML , "clamav-de...@lists.clamav.net" , "clamav-annou...@lists.clamav.net" Subject: [Clamav-devel] ClamAV?? blog: ClamAV 0.103.0 release candidate x-mailer: Apple Mail (2.3608.120.23.2.1) > > https://blog.clamav.net/2020/08/clamav-01030-release-candidate.html > <https://blog.clamav.net/2020/08/clamav-01030-release-candidate.html> > > ClamAV 0.103.0 release candidate > > Today we are pleased to announce the ClamAV 0.103.0 release candidate > <https://www.clamav.net/downloads>! > > Please help us validate this release. We need your feedback so let us know > what you find and join us on the clamav mailing list > <https://lists.clamav.net/mailman/listinfo/clamav-users>, in #clamav on > irc.freenode.net, or on our Discord <https://discord.gg/sGaxA5Q>, which is > bridged with our IRC. > > Please submit bugs to on our Bugzilla > <https://bugzilla.clamav.net/enter_bug.cgi?product=ClamAV>. > > ClamAV 0.103.0 includes the following improvements and changes. > > Major changes > > clamd can now reload the signature database without blocking scanning. This > multi-threaded database reload improvement was made possible thanks to a > community effort. > Non-blocking database reloads are now the default behavior. Some systems that > are more constrained on RAM may need to disable non-blocking reloads as it > will temporarily consume 2x as much memory. For this purpose we have added a > new clamd config option ConcurrentDatabaseReload which may be set to no. > > Special thanks to the following for making this feature a reality: > Alberto Wu > Alexander Sulfrian > Arjen de Korte > David Heidelberg > Ged Haywood > Julius Plenz > Michael Orlitzky > > Thank you all for your patience waiting for this feature. > > Notable changes > > > The DLP module has been enhanced with additional credit card ranges and a new > engine option which allows ClamAV to alert only on credit cards (and not, for > instance, gift cards) when scannning with the DLP module. This feature > enhancement was made by John Schember, with input from Alexander Sulfrian. > > Support for Adobe Reader X PDF encryption, an overhaul of PNG scanning to > detect PNG specific exploits, and a major change to GIF parsing which makes > it more tolerant to problematic files and adds the ability to scan overlays, > all thanks to work and patches submitted by Aldo Mazzeo. > > clamdtop.exe now available for Windows users. Functionality is somewhat > limited when compared with clamdtop on Linux. PDCurses is required to build > clamdtop.exe for ClamAV on Windows. > > The phishing detection module will now print "Suspicious link found!" along > with the "Real URL" and "Display URL" each time phishing is detected. In a > future version, we would like to print out alert-related metadata like this > at the end of a scan, but for now this detail will help users understand why > a given file is being flagged as phishing. > > Added new *experimental* CMake build tooling. CMake is not yet recommended > for production builds. Our team would appreciate any assistance improving the > CMake build tooling so we can one day deprecate Autotools and remove the > Visual Studio solutions. > Please see the new CMake installation instructions found in INSTALL.cmake.md > for detailed instructions on how to build ClamAV with CMake. > > Added --ping and --wait options to the clamdscan and clamonacc client > applications. > The --ping (-p) command will attempt to ping clamd up to a specified maximum > number of attempts at an optional interval. If the interval isn't specified, > a default 1-second interval is used. It will exit with status code `0` when > it receives a PONG from clamd or status code `21` if the timeout expires > before it receives a response. > Example: > clamdscan -p 120 will attempt to ping clamd 120 at a 1 second interval. > The --wait (-w) command will wait up to 30 seconds for clamd to start. This > option may be used in tandem with the --ping option to customize the max # of > attempts and the attempt interval. As with --ping, the scanning client may > exit with status code 21 if the timeout expires before a connection is made > to clamd. > Example: > clamdscan -p 30:2 -w will attempt a scan, waiting up to 60 seconds for > clamd to start and receive the scan request. > The ping-and-wait feature is particularly useful for those wishing to start > clamd and start clamonacc at startup,
Re: [jes...@cisco.com: [Clamav-announce] ClamAV? blog: ClamAV 0.102.4 security patch released]
On 2020-07-16 22:52, The Doctor via freebsd-ports wrote:
Heads up!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248027
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248028
- Forwarded message from "Joel Esler (jesler)"
-
Date: Thu, 16 Jul 2020 19:32:35 +
From: "Joel Esler (jesler)"
To: ClamAV users ML , ClamAV Development
, "clamav-annou...@lists.clamav.net"
Subject: [Clamav-announce] ClamAV? blog: ClamAV 0.102.4 security patch
released
x-mailer: Apple Mail (2.3608.120.23.2.1)
[rest snipped]
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[jes...@cisco.com: [Clamav-announce] ClamAV? blog: ClamAV 0.102.4 security patch released]
Heads up!
- Forwarded message from "Joel Esler (jesler)" -
Date: Thu, 16 Jul 2020 19:32:35 +
From: "Joel Esler (jesler)"
To: ClamAV users ML , ClamAV Development
, "clamav-annou...@lists.clamav.net"
Subject: [Clamav-announce] ClamAV? blog: ClamAV 0.102.4 security patch released
x-mailer: Apple Mail (2.3608.120.23.2.1)
> https://blog.clamav.net/2020/07/clamav-01024-security-patch-released.html
> <https://blog.clamav.net/2020/07/clamav-01024-security-patch-released.html>
ClamAV 0.102.4 is out now. Users can head over to clamav.net/downloads
<https://www.clamav.net/downloads> to download the release materials.
ClamAV 0.102.4 is a bug patch release to address the following issues:
CVE-2020-3350
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3350>Fixed a
vulnerability a malicious user could exploit to replace a scan target's
directory with a symlink to another path to trick clamscan, clamdscan, or
clamonacc into removing or moving a different file (such as a critical system
file). The issue would affect users that use the --move or --remove options for
clamscan, clamdscan and clamonacc.
For more information about AV quarantine attacks using links, see RACK911 Lab's
report
<https://www.rack911labs.com/research/exploiting-almost-every-antivirus-software>.
CVE-2020-3327
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3327>Fixed a
vulnerability in the ARJ archive-parsing module in ClamAV 0.102.3 that could
cause a denial-of-service (DoS) condition. Improper bounds checking resulted in
an out-of-bounds read that could cause a crash. The previous fix for this CVE
in version 0.102.3 was incomplete. This fix correctly resolves the issue.
CVE-2020-3481
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3481>Fixed a
vulnerability in the EGG archive module in ClamAV 0.102.0 - 0.102.3 that could
cause a denial-of-service (DoS) condition. Improper error handling could cause
a crash due to a NULL pointer dereference. This vulnerability is mitigated for
those using the official ClamAV signature databases because the file type
signatures in daily.cvd will not enable the EGG archive parser in affected
versions.
We will be publishing a release candidate for version 0.103.0 in the next
couple of weeks. Stay tuned!
--
Joel Esler
Manager, Communities Division
Cisco Talos Intelligence Group
http://www.talosintelligence.com | https://www.snort.org
_______
clamav-announce mailing list
clamav-annou...@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-announce
http://www.clamav.net/contact.html#ml
- End forwarded message -
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b
We were not instructed to succumb to the world. -unknown
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: latest Makefile breaks compilation of security/clamav if base is lacking sendmail
Hello Michael,
Thank you for bug report and patch. I confirmed your patch fixes the
problem with 12.1-RELEASE.
From: Michael Grimm
Subject: latest Makefile breaks compilation of security/clamav if base is
lacking sendmail
Date: Sun, 5 Jul 2020 15:37:13 +0200
> I managed to get compilation working with the attached, surely crude and
> dirty hack (due to my lack of knowledge regarding ports Makefiles), by adding
> 'MILTER_LDFLAGS= -L${LOCALBASE}/lib' and 'MILTER_CFLAGS=
> -I${LOCALBASE}/include' in order to help finding relevant files from port
> mail/libmilter.
>
> What worries my somehow, although clamav is working as usual, is the
> following part in poudrier's log:
>
> checking for mi_stop in -lmilter… yes
> checking libmilter/mfapi.h usability… yes
> checking libmilter/mfapi.h presence… no
> configure: WARNING: libmilter/mfapi.h: accepted by the compiler,
> rejected by the preprocessor!
> configure: WARNING: libmilter/mfapi.h: proceeding with the compiler's
> result
> checking for libmilter/mfapi.h... yes
>
>
> Here my question: Is this the right way to fix this issue?
I'm not sure why configure script produces such warning messages. But
mail/libmilter surely installs ${PREFIX}/lib/libmilter/mfapi.h and
configure script correctly detects it anyway. Therefore I don't think
this warning message is of much concern.
And I submitted a bit modified patch as following bug report.
security/clamav: Fix build after r541115 when base system is build
with 'WITHOUT_SENDMAIL=yes'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247792
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
latest Makefile breaks compilation of security/clamav if base is lacking sendmail
Hi,
I am running 12.1-STABLE (r362940), ports head (541271) and compile all my
ports with poudriere-devel
My /etc/src.conf contains …
WITHOUT_SENDMAIL=yes
… thus I do not have /usr/lib/libmilter.so in base.
The recent modification of security/clamav/Makefile breaks my setup (again [1],
see
https://lists.freebsd.org/pipermail/freebsd-ports/2018-December/115116.html).
Error message ...
checking for mi_stop in -lmilter… no
configure: error: Cannot find libmilter
...
*** Error code 1
… and after having that fixed another error:
checking for mi_stop in -lmilter… yes
checking libmilter/mfapi.h usability… no
checking libmilter/mfapi.h presence… no
checking for libmilter/mfapi.h… no
configure: error: Please install mfapi.h from the sendmail distribution
===> Script "configure" failed unexpectedly.
...
*** Error code 1
I managed to get compilation working with the attached, surely crude and dirty
hack (due to my lack of knowledge regarding ports Makefiles), by adding
'MILTER_LDFLAGS= -L${LOCALBASE}/lib' and 'MILTER_CFLAGS=
-I${LOCALBASE}/include' in order to help finding relevant files from port
mail/libmilter.
What worries my somehow, although clamav is working as usual, is the following
part in poudrier's log:
checking for mi_stop in -lmilter… yes
checking libmilter/mfapi.h usability… yes
checking libmilter/mfapi.h presence… no
configure: WARNING: libmilter/mfapi.h: accepted by the compiler,
rejected by the preprocessor!
configure: WARNING: libmilter/mfapi.h: proceeding with the compiler's
result
checking for libmilter/mfapi.h... yes
Here my question: Is this the right way to fix this issue?
Thanks and regards,
Michael
[1] no pun intended
patch
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[jes...@cisco.com: [Clamav-announce] ClamAV?? blog: ClamAV 0.102.2 security patch released]
Heads up security/clamav team. - Forwarded message from "Joel Esler (jesler)" - Date: Wed, 5 Feb 2020 17:29:00 + From: "Joel Esler (jesler)" To: "clamav-annou...@lists.clamav.net" , "clamav-us...@lists.clamav.net" , "clamav-de...@lists.clamav.net" Subject: [Clamav-announce] ClamAV?? blog: ClamAV 0.102.2 security patch released x-mailer: Apple Mail (2.3608.60.0.2.5) https://blog.clamav.net/2020/02/clamav-01022-security-patch-released.html Today, we're publishing 0.102.2. Navigate to ClamAV's downloads<http://www.clamav.net/downloads> page to download the release materials. 0.102.2 ClamAV 0.102.2 is a security patch release to address the following issues. * CVE-2020-3123<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3123>: A denial-of-service (DoS) condition may occur when using the optional credit card data-loss-prevention (DLP) feature. Improper bounds checking of an unsigned variable resulted in an out-of-bounds read, which causes a crash. * Significantly improved the scan speed of PDF files on Windows. * Re-applied a fix to alleviate file access issues when scanning RAR files in downstream projects that use libclamav where the scanning engine is operating in a low-privilege process. This bug was originally fixed in 0.101.2 and the fix was mistakenly omitted from 0.102.0. * Fixed an issue where freshclam failed to update if the database version downloaded is one version older than advertised. This situation may occur after a new database version is published. The issue affected users downloading the whole CVD database file. * Changed the default freshclam ReceiveTimeout setting to 0 (infinite). The ReceiveTimeout had caused needless database update failures for users with slower internet connections. * Correctly display the number of kilobytes (KiB) in progress bar and reduced the size of the progress bar to accommodate 80-character width terminals. * Fixed an issue where running freshclam manually causes a daemonized freshclam process to fail when it updates because the manual instance deletes the temporary download directory. The freshclam temporary files will now download to a unique directory created at the time of an update instead of using a hardcoded directory created/destroyed at the program start/exit. * Fix for freshclam's OnOutdatedExecute config option. * Fixes a memory leak in the error condition handling for the email parser. * Improved bound checking and error handling in ARJ archive parser. * Improved error handling in PDF parser. * Fix for memory leak in byte-compare signature handler. * Updates to the unit test suite to support libcheck 0.13. * Updates to support autoconf 2.69 and automake 1.15. Special thanks to the following people for code contributions and bug reports: * Antoine Desch??nes * Eric Lindblad * Gianluigi Tiesi * Tuomo Soini Please join us on the ClamAV mailing lists<https://www.clamav.net/contact#ml> for further discussion. Thanks! _______ clamav-announce mailing list clamav-annou...@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-announce http://www.clamav.net/contact.html#ml - End forwarded message - -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Sometimes it is the greediest giving things away. -unknown ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav
On Wed, Aug 07, 2019 at 07:43:17PM +0200, Florian Smeets via freebsd-ports wrote: > On 7. Aug 2019, at 04:02, Kubilay Kocak wrote: > > > > On 7/08/2019 7:57 am, The Doctor via freebsd-ports wrote: > >> Wehen Will clamav be updated? > >> I understand there is a security issue? > > > > The best / most effective method to report/request security releases or > > updates is in Bugzilla, I've created one for the ClamAV 0.101.3 version > > (security) update) here: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239684 > > FWIW, the fix in 0.101.3 seems to be incomplete. I guess there will be > another version soon. > Fix what we can now and propose a ptch for this next flaw. > https://www.openwall.com/lists/oss-security/2019/08/06/3 > <https://www.openwall.com/lists/oss-security/2019/08/06/3> > > Florian > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Flattery is like cologne water, to be smelt of, not swallowed. -Josh Billings ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav
On 7. Aug 2019, at 04:02, Kubilay Kocak wrote: > > On 7/08/2019 7:57 am, The Doctor via freebsd-ports wrote: >> Wehen Will clamav be updated? >> I understand there is a security issue? > > The best / most effective method to report/request security releases or > updates is in Bugzilla, I've created one for the ClamAV 0.101.3 version > (security) update) here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239684 FWIW, the fix in 0.101.3 seems to be incomplete. I guess there will be another version soon. https://www.openwall.com/lists/oss-security/2019/08/06/3 <https://www.openwall.com/lists/oss-security/2019/08/06/3> Florian ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav
On 7/08/2019 7:57 am, The Doctor via freebsd-ports wrote: Wehen Will clamav be updated? I understand there is a security issue? The best / most effective method to report/request security releases or updates is in Bugzilla, I've created one for the ClamAV 0.101.3 version (security) update) here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239684 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav
On Wed, Aug 07, 2019 at 09:52:28AM +1000, Dewayne Geraghty wrote:
> On 7/08/2019 7:57 am, The Doctor via freebsd-ports wrote:
> > Wehen Will clamav be updated?
> >
> > I understand there is a security issue?
> >
> Thank-you for sharing the issue. I usually log a PR to raise attention,
> but it can sometimes take a while for CVE's to be addressed,
> eg re heimdal https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238635
>
> So I usually tweak the Makefile, build and use then log the PR.
>
> Thanks to you, I'm now running clamav 101.3. Some testing then into
> production ;)
>
> Kind regards, Dewayne.
>
Good work sir.
I usually stay in touch with clamav and other since my BSD/OS days
even if I abondonned BSD/OS 3 years ago.
> --- /usr/ports/security/clamav/Makefile (revision 508231)
> +++ /usr/ports/security/clamav/Makefile (working copy)
> @@ -1,8 +1,8 @@
> # $FreeBSD$
>
> PORTNAME= clamav
> -PORTVERSION= 0.101.2
> -PORTEPOCH= 1
> +PORTVERSION= 0.101.3
> +#PORTEPOCH=1
> CATEGORIES=security
> MASTER_SITES= https://www.clamav.net/downloads/production/
>
> @@ -38,7 +38,7 @@
> --disable-dependency-tracking \
> --enable-clamdtop
>
> -CFLAGS_i386= -march=i486
> +# 201904 why? I use prescott or haswel! CFLAGS_i386= -march=i486
> CPPFLAGS+= -I${LOCALBASE}/include
>
> # This port has a problem with -pthread,
> Index: /usr/ports/security/clamav/distinfo
> =======
> --- /usr/ports/security/clamav/distinfo (revision 508231)
> +++ /usr/ports/security/clamav/distinfo (working copy)
> @@ -1,3 +1,3 @@
> -TIMESTAMP = 1553639567
> -SHA256 (clamav-0.101.2.tar.gz) =
> 0a12ebdf6ff7a74c0bde2bdc2b55cae33449e6dd953ec90824a9e01291277634
> -SIZE (clamav-0.101.2.tar.gz) = 21722932
> +TIMESTAMP = 1565134915
> +SHA256 (clamav-0.101.3.tar.gz) =
> 68d42aac4a9cbde293288533a9a3c3d55863de38f2b8707c1ef2d987b1260338
> +SIZE (clamav-0.101.3.tar.gz) = 21389753
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism
Flattery is like cologne water, to be smelt of, not swallowed. -Josh Billings
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav
On Wed, 7 Aug 2019 at 10:33, The Doctor via freebsd-ports wrote: > > Wehen Will clamav be updated? > > I understand there is a security issue? The correct thing to do is to politely ask the maintainer as to the state of the port, and request an update. Alternatively, you can submit a patch to the port to bring it up to date. Cheers. -- Jonathan Chen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Clamav
Wehen Will clamav be updated? I understand there is a security issue? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Flattery is like cologne water, to be smelt of, not swallowed. -Josh Billings ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Yasuhiro KIMURA wrote: > Thank you for checking patch. Then I'll submit this patch to > Bugzilla. I may take for a while but will be committed to ports > repository. Thanks. "One more thing" ;-) Your patch will work, and thinking about the maturity of libmilter, your patch will be an appropriate one. I am thinking about a more "future safe" solution for security/clamav-milter: #) add an OPTION to security/clamav-milter's Makefile whether to use libmilter from base or ports #) make the default to use port mail/libmilter #) because the latter will allow to automatically follow newest developments of libmilter and clamav ports Don't get me wrong, you are the maintainer, thus, it is completely up to you! Thanks again and kind regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 23:11:09 +0100 > Thank you very, very much, your patch works in my case (lacking sendmail in > base). > > mike> poudriere bulk -j stable -C security/clamav-milter > > … will run to completion, see: > > ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so > - not found > ===> Installing existing package /packages/All/libmilter-8.15.2_1.txz > [stable-default-job-01] Installing libmilter-8.15.2_1... > [stable-default-job-01] Extracting libmilter-8.15.2_1: .. done > ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so > - found (/usr/local/lib/libmilter.so) > ===> Returning to build of clamav-milter-0.100.2,1 > > Thank you very much. Your patch is much more elegant then my one ;-) Thank you for checking patch. Then I'll submit this patch to Bugzilla. I may take for a while but will be committed to ports repository. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Yasuhiro KIMURA wrote: > From: Michael Grimm >> If I do set the option to create the milter interface (sp?) in >> security/clamav I do run into the same error "Cannot find libmilter". > > Thank you for replay. Then please try following patch. With it > security/clamav (and security/clamav-milter) should depend on > mail/libmilter only when there isn't sendmail in base system. Thank you very, very much, your patch works in my case (lacking sendmail in base). mike> poudriere bulk -j stable -C security/clamav-milter … will run to completion, see: ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so - not found ===> Installing existing package /packages/All/libmilter-8.15.2_1.txz [stable-default-job-01] Installing libmilter-8.15.2_1... [stable-default-job-01] Extracting libmilter-8.15.2_1: .. done ===> clamav-milter-0.100.2,1 depends on shared library: libmilter.so - found (/usr/local/lib/libmilter.so) ===> Returning to build of clamav-milter-0.100.2,1 Thank you very much. Your patch is much more elegant then my one ;-) With kind regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 22:20:04 +0100 > If I do set the option to create the milter interface (sp?) in > security/clamav I do run into the same error "Cannot find libmilter". > > I didn't try to build security/clamav without milter support, though. Due to > obvious reasons, because I do need the milter support for postfix. Thank you for replay. Then please try following patch. With it security/clamav (and security/clamav-milter) should depend on mail/libmilter only when there isn't sendmail in base system. Index: Makefile === --- Makefile(revision 488063) +++ Makefile(working copy) @@ -15,6 +15,10 @@ LIB_DEPENDS= libltdl.so:devel/libltdl \ libcurl.so:ftp/curl +.if !exists(/usr/lib/libmilter.so) +LIB_DEPENDS+= libmilter.so:mail/libmilter +.endif + USES= cpe gmake gnome libtool ncurses pathfix pkgconfig ssl USE_RC_SUBR= clamav-clamd clamav-freshclam USE_LDCONFIG= yes Best Regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Yasuhiro KIMURA wrote: > > From: Michael Grimm >> See my last mail. I do not have sendmail compiled for base, thus I am >> lacking libmilter.so.X in my poudriere jail. >> Yes, that is non-default ;-) My port has default settings. > > Sorry, I read only first mail. No need to be sorry, really. > Then I have another question. Does build of security/clamav, master > port of security/clamav-milter, also fail on your environment? If I do set the option to create the milter interface (sp?) in security/clamav I do run into the same error "Cannot find libmilter". I didn't try to build security/clamav without milter support, though. Due to obvious reasons, because I do need the milter support for postfix. BTW: Please have a look at the mail/spamass-milter port. This port builds against the libmilter port as well. Thanks and regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
From: Michael Grimm Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 21:47:50 +0100 > See my last mail. I do not have sendmail compiled for base, thus I am lacking > libmilter.so.X in my poudriere jail. > Yes, that is non-default ;-) My port has default settings. Sorry, I read only first mail. Then I have another question. Does build of security/clamav, master port of security/clamav-milter, also fail on your environment? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Yasuhiro KIMURA wrote: > And build of security/clamav-milter succeeded with all cases. > > Do you use any non-default setting about clamav-milter itself or any > of its dependencies? See my last mail. I do not have sendmail compiled for base, thus I am lacking libmilter.so.X in my poudriere jail. Yes, that is non-default ;-) My port has default settings. Regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Hello Michael. From: Michael Grimm Subject: security/clamav-milter fails to compile (preliminary patch included) Date: Sat, 22 Dec 2018 17:14:11 +0100 > after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to > compile: > > configure: error: Cannot find libmilter > ===> Script "configure" failed unexpectedly. > Please report the problem to y...@utahime.org [maintainer] and attach > the > > "/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log" > including the output of the failure of your make command. Also, it > might be > a good idea to provide an overview of all packages installed on your > system > (e.g. a /usr/local/sbin/pkg-static info -g -Ea). > *** Error code 1 > > Stop. I tried build with poudriere under following conditions. Host: FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT r342280 GENERIC amd64 Poudriere: 3.2.8 Jails: 1. 13.0-CURRENT r342280 amd64 Build from source tree. 2. 12.0-STABLE r341991 amd64 Installed from https://download.freebsd.org/ftp/snapshots/amd64/12.0-STABLE/ 3. 12.0-RELEASE-p1 amd64 Installed from https://download.freebsd.org/ftp/releases/amd64/12.0-RELEASE/ 4. 11.2-STABLE r341995 amd64 Installed from https://download.freebsd.org/ftp/snapshots/amd64/11.2-STABLE/ 5. 11.2-RELEASE-p7 amd64 Installed from https://download.freebsd.org/ftp/releases/amd64/11.2-RELEASE/ Ports tree: r488063 And build of security/clamav-milter succeeded with all cases. Do you use any non-default setting about clamav-milter itself or any of its dependencies? --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Carmel NY wrote: > On Sat, 22 Dec 2018 20:23:39 +0100, Michael Grimm stated: >> Hmm, I do get the feeling that you misunderstand what I am telling you. See, below. >> Next, that poudriere jail keeps a copy of a resulting "make buildworld" run >> of base. This jail is lacking any binary/library of ports running on my >> machine. Thus, libmilter.so is missing as well: >> >> mike> find /usr/home/poudriere/jails/stable -name "libmilter.so*" -ls >> mike> > > Michael, I am certainly not a guru regarding poudriere, or system updating. Sorry, I didn't want you to believe I am getting "personal". Sorry. > I just now what I was told. Perhaps Matthew Seaman or > somebody with more knowledge about this than I can assist you. > > All I know for certain is that I was told to update the poudriere jail, I > actually deleted the old one and created a new one, and then do a forced > rebuild of all installed ports. The following worked for me, after I created > a new jail. Obviously, the jail name here is mine. > > portmaster --list-origins | sort -d | tee "~/portlist.txt" > poudriere bulk -c -f "~/portlist.txt" -j "12amd64" > pkg upgrade -y > > ~ $ poudriere jail -l > JAILNAME VERSION ARCH METHOD TIMESTAMP PATH > 12amd64 12.0-RELEASE-p1 amd64 ftp2018-12-21 18:25:41 > /usr/local/poudriere/jails/12amd64 > > ~ $ locate libmilter.so > /usr/lib/libmilter.so > /usr/lib/libmilter.so.6 > /usr/lib32/libmilter.so > /usr/lib32/libmilter.so.6 > /usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so > /usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so.6 > /usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so > /usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so.6 See, that is what I was describing. You do have sendmail installed in base, and thus, the libmilter library will make it into your poudriere build jail, and security/clamav-milter will find a libmilter library -in base!- during compilation and will link this library. Thus, this port will compile in your case, because it is using libmilter.so from base, not from the mail/libmilter port! FYI: I did trigger this bug because I do compile base without sendmail (WITHOUT_SENDMAIL=yes in /etc/src.conf)! Thus, no "chance finding" of /usr/lib/libmilter.so.X in base aka my poudriere jail during my compilation. Regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
On Sat, 22 Dec 2018 20:23:39 +0100, Michael Grimm stated: >Carmel NY wrote: >> On Sat, 22 Dec 2018 18:13:51 +0100, Michael Grimm stated: >>> Michael Grimm wrote: > >>>> I am using poudriere to build my ports. Within a poudriere jail used to >>>> compile the clamav-libmilter port no libmilter.so can be found by >>>> configure (see error message above) unless you tellclamav-libmilter's >>>> Makefile to depend on it and thus pre-install it in this jail. >>> >>> Sorry, s/clamav-libmilter/clamav-milter/g >> >> Did you update the poudriere jail to 12.0? I had a similar problem until I >> undated it and did a forced rebuild of everything. In fact, I found it >> easier and quicker to simple delete the existing jail and create a new >> one. > >Hmm, I do get the feeling that you misunderstand what I am telling you. > >My poudriere's jail follows /usr/src. Thus at every rebuild of my OS (I do >that every other week because I am following STABLE-12) my jail gets >upgraded as well: > > mike> poudriere jail -l > JAILNAME VERSION ARCH METHOD TIMESTAMP > PATH stable 12.0-STABLE 1200500 amd64 src=/usr/src 2018-12-22 > 18:19:50 /usr/home/poudriere/jails/stable > >Next, that poudriere jail keeps a copy of a resulting "make buildworld" run >of base. This jail is lacking any binary/library of ports running on my >machine. Thus, libmilter.so is missing as well: > > mike> find /usr/home/poudriere/jails/stable -name "libmilter.so*" -ls > mike> > >Now, poudriere will create (cpdup) as many jails >from /usr/home/poudriere/jails/stable as told to use builders. This "OS >copy" is lacking the needed libmilter library as well, when poudriere is >trying to build security/clamav-milter. And it will fail without indicating >that there is a dependency for yet another port, namely mail/libmilter. My >proposed patch will deal with that dependency. > >YMMV, but IMHO, a port shouldn't rely on pre-installed libraries from base >or other ports. Thus it shouldn't need a "forced rebuild of everything". > >Correct me if I am mistaken, but IIRC the libmilter library used to be part >of sendmail in base. This has been modified in FBSD 12, again IIRC [1]. > >Regards, >Michael > > >[1] https://svnweb.freebsd.org/ports?view=revision=473663 Michael, I am certainly not a guru regarding poudriere, or system updating. I just now what I was told. Perhaps Matthew Seaman or somebody with more knowledge about this than I can assist you. All I know for certain is that I was told to update the poudriere jail, I actually deleted the old one and created a new one, and then do a forced rebuild of all installed ports. The following worked for me, after I created a new jail. Obviously, the jail name here is mine. portmaster --list-origins | sort -d | tee "~/portlist.txt" poudriere bulk -c -f "~/portlist.txt" -j "12amd64" pkg upgrade -y ~ $ poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH 12amd64 12.0-RELEASE-p1 amd64 ftp2018-12-21 18:25:41 /usr/local/poudriere/jails/12amd64 ~ $ locate libmilter.so /usr/lib/libmilter.so /usr/lib/libmilter.so.6 /usr/lib32/libmilter.so /usr/lib32/libmilter.so.6 /usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so /usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so.6 /usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so /usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so.6 Good Luck! -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Carmel NY wrote: > On Sat, 22 Dec 2018 18:13:51 +0100, Michael Grimm stated: >> Michael Grimm wrote: >>> I am using poudriere to build my ports. Within a poudriere jail used to >>> compile the clamav-libmilter port no libmilter.so can be found by >>> configure (see error message above) unless you tellclamav-libmilter's >>> Makefile to depend on it and thus pre-install it in this jail. >> >> Sorry, s/clamav-libmilter/clamav-milter/g > > Did you update the poudriere jail to 12.0? I had a similar problem until I > undated it and did a forced rebuild of everything. In fact, I found it easier > and quicker to simple delete the existing jail and create a new one. Hmm, I do get the feeling that you misunderstand what I am telling you. My poudriere's jail follows /usr/src. Thus at every rebuild of my OS (I do that every other week because I am following STABLE-12) my jail gets upgraded as well: mike> poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH stable 12.0-STABLE 1200500 amd64 src=/usr/src 2018-12-22 18:19:50 /usr/home/poudriere/jails/stable Next, that poudriere jail keeps a copy of a resulting "make buildworld" run of base. This jail is lacking any binary/library of ports running on my machine. Thus, libmilter.so is missing as well: mike> find /usr/home/poudriere/jails/stable -name "libmilter.so*" -ls mike> Now, poudriere will create (cpdup) as many jails from /usr/home/poudriere/jails/stable as told to use builders. This "OS copy" is lacking the needed libmilter library as well, when poudriere is trying to build security/clamav-milter. And it will fail without indicating that there is a dependency for yet another port, namely mail/libmilter. My proposed patch will deal with that dependency. YMMV, but IMHO, a port shouldn't rely on pre-installed libraries from base or other ports. Thus it shouldn't need a "forced rebuild of everything". Correct me if I am mistaken, but IIRC the libmilter library used to be part of sendmail in base. This has been modified in FBSD 12, again IIRC [1]. Regards, Michael [1] https://svnweb.freebsd.org/ports?view=revision=473663 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
On Sat, 22 Dec 2018 18:13:51 +0100, Michael Grimm stated: >Michael Grimm wrote: > >> I am using poudriere to build my ports. Within a poudriere jail used to >> compile the clamav-libmilter port no libmilter.so can be found by >> configure (see error message above) unless you tellclamav-libmilter's >> Makefile to depend on it and thus pre-install it in this jail. > >Sorry, s/clamav-libmilter/clamav-milter/g > >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Did you update the poudriere jail to 12.0? I had a similar problem until I undated it and did a forced rebuild of everything. In fact, I found it easier and quicker to simple delete the existing jail and create a new one. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Michael Grimm wrote: > I am using poudriere to build my ports. Within a poudriere jail used to > compile the clamav-libmilter port no libmilter.so can be found by configure > (see error message above) unless you tellclamav-libmilter's Makefile to > depend on it and thus pre-install it in this jail. Sorry, s/clamav-libmilter/clamav-milter/g ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
Carmel NY wrote: > On Sat, 22 Dec 2018 17:14:11 +0100, Michael Grimm stated: >> after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to >> compile: >> >> configure: error: Cannot find libmilter >> ===> Script "configure" failed unexpectedly. >> Please report the problem to y...@utahime.org [maintainer] and >> attach the >> >> "/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log" >> including the output of the failure of your make command. Also, it >> might be a good idea to provide an overview of all packages >> installed on your system (e.g. a /usr/local/sbin/pkg-static info -g >> -Ea). *** Error code 1 >> >> Stop. This happens when compiled by poudriere. > Clamav-milter updated fine for me once I updated all of the installed ports > on my system. I am assuming that you did update your ports tree and then > update all of the ports on your system. If you don't, clamav-milter, and > several other ports, will fail. I am not quite sure if I do understand you correctly. I am using poudriere to build my ports. Within a poudriere jail used to compile the clamav-libmilter port no libmilter.so can be found by configure (see error message above) unless you tell clamav-libmilter's Makefile to depend on it and thus pre-install it in this jail. Regards, Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/clamav-milter fails to compile (preliminary patch included)
On Sat, 22 Dec 2018 17:14:11 +0100, Michael Grimm stated:
>Hi,
>
>after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to
>compile:
>
> configure: error: Cannot find libmilter
> ===> Script "configure" failed unexpectedly.
> Please report the problem to y...@utahime.org [maintainer] and
> attach the
>
> "/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log"
> including the output of the failure of your make command. Also, it
> might be a good idea to provide an overview of all packages
> installed on your system (e.g. a /usr/local/sbin/pkg-static info -g
> -Ea). *** Error code 1
>
> Stop.
>
>It looks to me that starting STABLE-12 one needs to add library dependency
>to mail/libmilter:
>
>___ patch _
>--- security/clamav/Makefile.old 2018-12-22 16:43:04.91388 +0100
>+++ security/clamav/Makefile 2018-12-22 16:51:53.618789000 +0100
>@@ -13,7 +13,8 @@
> LICENSE_FILE= ${WRKSRC}/COPYING
>
> LIB_DEPENDS= libltdl.so:devel/libltdl \
>- libcurl.so:ftp/curl
>+ libcurl.so:ftp/curl \
>+ libmilter.so:mail/libmilter
>
> USES= cpe gmake gnome libtool ncurses pathfix pkgconfig ssl
> USE_RC_SUBR= clamav-clamd clamav-freshclam
>___ patch _
>
>This patch works for me.
>
>BUT: I do not know if this is the right way to fix it, because this patch is
>applied to security/clamav which in turn is used from security/clamav-milter
>by simply adding OPTIONS_SLAVE+= MILTER. Thus a libmilter dependency
>will be added to users of plain security/clamav port as well.
>
>Regards,
>Michael
Clamav-milter updated fine for me once I updated all of the installed ports
on my system. I am assuming that you did update your ports tree and then
update all of the ports on your system. If you don't, clamav-milter, and
several other ports, will fail.
--
Carmel
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/clamav-milter fails to compile (preliminary patch included)
Hi,
after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to
compile:
configure: error: Cannot find libmilter
===> Script "configure" failed unexpectedly.
Please report the problem to y...@utahime.org [maintainer] and attach
the
"/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log"
including the output of the failure of your make command. Also, it
might be
a good idea to provide an overview of all packages installed on your
system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1
Stop.
It looks to me that starting STABLE-12 one needs to add library dependency to
mail/libmilter:
___ patch _____
--- security/clamav/Makefile.old2018-12-22 16:43:04.913880000 +0100
+++ security/clamav/Makefile2018-12-22 16:51:53.618789000 +0100
@@ -13,7 +13,8 @@
LICENSE_FILE= ${WRKSRC}/COPYING
LIB_DEPENDS= libltdl.so:devel/libltdl \
- libcurl.so:ftp/curl
+ libcurl.so:ftp/curl \
+ libmilter.so:mail/libmilter
USES= cpe gmake gnome libtool ncurses pathfix pkgconfig ssl
USE_RC_SUBR= clamav-clamd clamav-freshclam
___ patch _
This patch works for me.
BUT: I do not know if this is the right way to fix it, because this patch is
applied to security/clamav which in turn is used from security/clamav-milter by
simply adding OPTIONS_SLAVE+= MILTER. Thus a libmilter dependency will be
added to users of plain security/clamav port as well.
Regards,
Michael
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ClamAV Port Version Regression?
Perfect! Thanks for the replies and the clarification, guys!
On 12/11/18 11:21 AM, Stefan Esser wrote:
> Am 11.12.18 um 18:51 schrieb Janky Jay, III:
>> Hi All,
>>
>> After a portsnap to pull ${latest), I'm seeing the following:
>>
>> clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
>>
>> The version that is claiming to be the latest appears to be a version
>> regression. Am I wrong here? I checked the ClamAV site and it appears
>> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
>> possibly a revision issue that's causing this?
>
> The ,1 at the end of the port to be installed indicates a new port epoch,
> which is used to enforce an "upgrade" to a lower version number.
>
> This is typically done if a port upgrade has been revoked due to problems
> with the new version.
>
> In this particular case the commit log says:
>
> r487064 | antoine | 2018-12-09 18:33:26 +0100 (Sun, 09 Dec 2018) | 6 lines
>
> Downgrade to 0.100.2
> Upstream plans to release version 0.101.1 which fixes header issues in January
> 2019
>
> Regards, STefan
>
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
Re: ClamAV Port Version Regression?
Am 11.12.18 um 18:51 schrieb Janky Jay, III:
> Hi All,
>
> After a portsnap to pull ${latest), I'm seeing the following:
>
> clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
>
> The version that is claiming to be the latest appears to be a version
> regression. Am I wrong here? I checked the ClamAV site and it appears
> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
> possibly a revision issue that's causing this?
The ,1 at the end of the port to be installed indicates a new port epoch,
which is used to enforce an "upgrade" to a lower version number.
This is typically done if a port upgrade has been revoked due to problems
with the new version.
In this particular case the commit log says:
r487064 | antoine | 2018-12-09 18:33:26 +0100 (Sun, 09 Dec 2018) | 6 lines
Downgrade to 0.100.2
Upstream plans to release version 0.101.1 which fixes header issues in January
2019
Regards, STefan
signature.asc
Description: OpenPGP digital signature
Re: ClamAV Port Version Regression?,ClamAV Port Version Regression?
Hello Janky.
From: "Janky Jay, III"
Subject: ClamAV Port Version Regression?,ClamAV Port Version Regression?
Date: Tue, 11 Dec 2018 10:51:43 -0700
> After a portsnap to pull ${latest), I'm seeing the following:
>
> clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
>
> The version that is claiming to be the latest appears to be a version
> regression. Am I wrong here? I checked the ClamAV site and it appears
> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
> possibly a revision issue that's causing this?
The problem about libclamav API is found in 0.101.0.
http://lists.clamav.net/pipermail/clamav-users/2018-December/007236.html
This results in build error of some ports that depends on
security/clamav. So it is downgraded to 0.100.2 until 0.101.1 is
released.
---
Yasuhiro KIMURA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ClamAV Port Version Regression?
Hi All,
After a portsnap to pull ${latest), I'm seeing the following:
clamav-0.101.0_2 < needs updating (index has 0.100.2,1)
The version that is claiming to be the latest appears to be a version
regression. Am I wrong here? I checked the ClamAV site and it appears
version 0.101.0 is, in fact, the latest. So, I'm wondering if there was
possibly a revision issue that's causing this?
Regards,
Janky Jay, III
signature.asc
Description: OpenPGP digital signature
Re: Clamav upgrade to 0.100.0_1 broken on amd64 current
Rerunning testport in my poudriere 11.1 jail for clamav, I get the following: gmake check-TESTS gmake[3]: Entering directory '/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[4]: Entering directory '/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' PASS: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh PASS: check1_clamscan.sh PASS: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh gmake[5]: Entering directory '/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[5]: Nothing to be done for 'all'. gmake[5]: Leaving directory '/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' Testsuite summary for ClamAV 0.100.0 # TOTAL: 13 # PASS: 7 # SKIP: 6 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 So, what EXACT freebsd version are you running, and what EXACT set of options for clamav did you set? And what tool are you using to build clamav? Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 On 4/14/18, 8:22 PM, "Manfred Antar" <manfredan...@gmail.com> wrote: I tried to upgrade clamav to 0.100.0_1 and it fails during tests. If you disable the tests it will build and install but clamscan dumps core. Here is output of build with tests enabled: FAIL: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh FAIL: check1_clamscan.sh FAIL: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh gmake[6]: Entering directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[6]: Nothing to be done for 'all'. gmake[6]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' Testsuite summary for ClamAV 0.100.0 # TOTAL: 13 # PASS: 4 # SKIP: 6 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 See unit_tests/test-suite.log Please report to https://bugzilla.clamav.net/ gmake[5]: *** [Makefile:1089: test-suite.log] Error 1 gmake[5]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[4]: *** [Makefile:1197: check-TESTS] Error 2 gmake[4]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[3]: *** [Makefile:1352: check-am] Error 2 gmake[3]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[2]: *** [Makefile:756: check-recursive] Error 1 gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0' *** Error code 2 Stop. make[1]: stopped in /usr/ports/security/clamav *** Error code 1 Stop. make: stopped in /usr/ports/security/clamav clamav 0.99.4 builds and passes tests fine Manfred ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clamav upgrade to 0.100.0_1 broken on amd64 current
The full log is at:
http://home.lerctr.org:/data/p111-S-amd64-host-ports/2018-04-14_20h32m16s/logs/clamav-0.100.0_1.log
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
On 4/14/18, 8:36 PM, "Larry Rosenman" <l...@lerctr.org> wrote:
Rerunning testport in my poudriere 11.1 jail for clamav, I get the
following:
gmake check-TESTS
gmake[3]: Entering directory
'/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[4]: Entering directory
'/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
PASS: check_clamav
PASS: check_freshclam.sh
PASS: check_sigtool.sh
SKIP: check_unit_vg.sh
PASS: check1_clamscan.sh
PASS: check2_clamd.sh
PASS: check3_clamd.sh
PASS: check4_clamd.sh
SKIP: check5_clamd_vg.sh
SKIP: check6_clamd_vg.sh
SKIP: check7_clamd_hg.sh
SKIP: check8_clamd_hg.sh
SKIP: check9_clamscan_vg.sh
gmake[5]: Entering directory
'/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[5]: Nothing to be done for 'all'.
gmake[5]: Leaving directory
'/wrkdirs/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
Testsuite summary for ClamAV 0.100.0
# TOTAL: 13
# PASS: 7
# SKIP: 6
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
So, what EXACT freebsd version are you running, and what EXACT set of
options for clamav did you set?
And what tool are you using to build clamav?
Thanks!
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
On 4/14/18, 8:22 PM, "Manfred Antar" <manfredan...@gmail.com> wrote:
I tried to upgrade clamav to 0.100.0_1 and it fails during tests.
If you disable the tests it will build and install but clamscan dumps
core.
Here is output of build with tests enabled:
FAIL: check_clamav
PASS: check_freshclam.sh
PASS: check_sigtool.sh
SKIP: check_unit_vg.sh
FAIL: check1_clamscan.sh
FAIL: check2_clamd.sh
PASS: check3_clamd.sh
PASS: check4_clamd.sh
SKIP: check5_clamd_vg.sh
SKIP: check6_clamd_vg.sh
SKIP: check7_clamd_hg.sh
SKIP: check8_clamd_hg.sh
SKIP: check9_clamscan_vg.sh
gmake[6]: Entering directory
'/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[6]: Nothing to be done for 'all'.
gmake[6]: Leaving directory
'/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
====
Testsuite summary for ClamAV 0.100.0
# TOTAL: 13
# PASS: 4
# SKIP: 6
# XFAIL: 0
# FAIL: 3
# XPASS: 0
# ERROR: 0
See unit_tests/test-suite.log
Please report to https://bugzilla.clamav.net/
gmake[5]: *** [Makefile:1089: test-suite.log] Error 1
gmake[5]: Leaving directory
'/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[4]: *** [Makefile:1197: check-TESTS] Error 2
gmake[4]: Leaving directory
'/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[3]: *** [Makefile:1352: check-am] Error 2
gmake[3]: Leaving directory
'/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests'
gmake[2]: *** [Makefile:756: check-recursive] Error 1
gmake[2]: Leaving directory
'/usr/ports/security/clamav/work/clamav-0.100.0'
*** Error code 2
Stop.
make[1]: stopped in /usr/ports/security/clamav
*** Error code 1
Stop.
make: stopped in /usr/ports/security/clamav
clamav 0.99.4 builds and passes tests fine
Manfred
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Clamav upgrade to 0.100.0_1 broken on amd64 current
I tried to upgrade clamav to 0.100.0_1 and it fails during tests. If you disable the tests it will build and install but clamscan dumps core. Here is output of build with tests enabled: FAIL: check_clamav PASS: check_freshclam.sh PASS: check_sigtool.sh SKIP: check_unit_vg.sh FAIL: check1_clamscan.sh FAIL: check2_clamd.sh PASS: check3_clamd.sh PASS: check4_clamd.sh SKIP: check5_clamd_vg.sh SKIP: check6_clamd_vg.sh SKIP: check7_clamd_hg.sh SKIP: check8_clamd_hg.sh SKIP: check9_clamscan_vg.sh gmake[6]: Entering directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[6]: Nothing to be done for 'all'. gmake[6]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' Testsuite summary for ClamAV 0.100.0 # TOTAL: 13 # PASS: 4 # SKIP: 6 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 See unit_tests/test-suite.log Please report to https://bugzilla.clamav.net/ gmake[5]: *** [Makefile:1089: test-suite.log] Error 1 gmake[5]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[4]: *** [Makefile:1197: check-TESTS] Error 2 gmake[4]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[3]: *** [Makefile:1352: check-am] Error 2 gmake[3]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0/unit_tests' gmake[2]: *** [Makefile:756: check-recursive] Error 1 gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.100.0' *** Error code 2 Stop. make[1]: stopped in /usr/ports/security/clamav *** Error code 1 Stop. make: stopped in /usr/ports/security/clamav clamav 0.99.4 builds and passes tests fine Manfred ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "clamav-unofficial-sigs" error message
On 2017-06-26 13:26, Carmel NY wrote: On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated: On 2017-06-25 18:16, Carmel NY wrote: On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: From what I can see, the clamav-unofficial-sigs port works. It determines if there are updates or whether you have checked recently, so that you do not inadvertently dos the signature servers. What is NOT working, apparently, is clamav. Did you install clamav via ports? If it is installed, what is the clamscan_bin variable set to in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to be set to the correct path, for instance /usr/local/bin/clamscan. The correct path on your setup can be determined using 'which clamscan' From the "master.conf" file: # Custom Command Paths, these are detected with the which command when not set. Clamscan was commented out; however, the default setting was to /usr/bin/clamscan From what I can figure out, the "which" command worked fine outside of a CRON job, but was failing when clamav-unofficial-sigs.sh was run via CRON. I uncommented the "clamscan" setting and set it to point to the correct location. Now it works correctly. This is probably a bug, but I am not going to waste my time reporting it. The ports version of this program is very old. There have been five newer versions since its release. No doubt this problem has been corrected. The error message that you're getting has nothing to do with the version of the script that's available from the ports collection. Contrary to what you think, you would get the same error message with the latest version of the script (clamscan binary detection has remained exactly the same). You obviously did not set up PATH variable correctly for script invoking by cron daemon. This is the default setting: # Custom Command Paths, these are detected with the which command when not set # uname_bin="/usr/bin/uname" # clamscan_bin="/usr/bin/clamscan" # rsync_bin="/usr/bin/rsync" # wget_bin="/usr/bin/wget" # curl_bin="/usr/bin/curl" # gpg_bin="/usr/bin/gpg" I only needed to uncomment and change the "clamscan_bin" setting to get it working correctly when run via CRON. Since the other settings are not correct for a FreeBSD system, yet still work, I do believe it is a bug of some sorts. However, it is not worth arguing about. You did not set up PATH variable correctly in your crontab. This is not a bug in the script. Also, master.conf and os.conf files should not be modified, or you will end up with old versions of those files when updating to a new version of the port. All user changes should be placed in user.conf (this is mentioned in both pkg-message and ports/UPDATING). On a side note, you mentioned that you edited "master.conf" file. As I wrote in pkg-message, all user configuration changes should go in file "user.conf" file, in order to make updating the script easier. As far as updating the port to the latest version is concerned, the development of the script appeared to be on halt since there were no updates from august last year until march this year and now it is quiet once again. The original script ended up being abandoned and I'm more cautious this time, so that I don't end up wasting my time. I am not sure what that is supposed to mean. The postfix "stable" version is only updated approximately once a year. A program does not have to be updated every "X" number of days to be actively developed. In any case, there have been five new versions released since the one in the ports system was released. Certainly that would seem to indicate that something was happening with the application. That means exactly what I wrote. I don't want to waste my time, if forked version also ends up being abandoned. -- Regards, Marko Njezic - mr.maX @ MAX Interactive corp. Personal: http://www.markonjezic.com/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "clamav-unofficial-sigs" error message
On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated: >On 2017-06-25 18:16, Carmel NY wrote: >> On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: >> >>> From what I can see, the clamav-unofficial-sigs port works. It >>> determines if there are updates or whether you have checked >>> recently, so that you do not inadvertently dos the signature >>> servers. What is NOT working, apparently, is clamav. Did you >>> install clamav via ports? If it is installed, what is the >>> clamscan_bin variable set to >>> in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs >>> to be set to the correct path, for >>> instance /usr/local/bin/clamscan. The correct path on your setup >>> can be determined using 'which clamscan' >> >> From the "master.conf" file: >> >> # Custom Command Paths, these are detected with the which command >> when not set. >> >> Clamscan was commented out; however, the default setting was >> to /usr/bin/clamscan >> >> From what I can figure out, the "which" command worked fine outside >> of a CRON job, but was failing when clamav-unofficial-sigs.sh was >> run via CRON. I uncommented the "clamscan" setting and set it to >> point to the correct location. Now it works correctly. >> >> This is probably a bug, but I am not going to waste my time reporting >> it. The ports version of this program is very old. There have been >> five newer versions since its release. No doubt this problem has been >> corrected. > >The error message that you're getting has nothing to do with the >version of the script that's available from the ports collection. > >Contrary to what you think, you would get the same error message with >the latest version of the script (clamscan binary detection has >remained exactly the same). You obviously did not set up PATH variable >correctly for script invoking by cron daemon. This is the default setting: # Custom Command Paths, these are detected with the which command when not set # uname_bin="/usr/bin/uname" # clamscan_bin="/usr/bin/clamscan" # rsync_bin="/usr/bin/rsync" # wget_bin="/usr/bin/wget" # curl_bin="/usr/bin/curl" # gpg_bin="/usr/bin/gpg" I only needed to uncomment and change the "clamscan_bin" setting to get it working correctly when run via CRON. Since the other settings are not correct for a FreeBSD system, yet still work, I do believe it is a bug of some sorts. However, it is not worth arguing about. >On a side note, you mentioned that you edited "master.conf" file. As I >wrote in pkg-message, all user configuration changes should go in file >"user.conf" file, in order to make updating the script easier. > >As far as updating the port to the latest version is concerned, the >development of the script appeared to be on halt since there were no >updates from august last year until march this year and now it is >quiet once again. The original script ended up being abandoned and I'm >more cautious this time, so that I don't end up wasting my time. I am not sure what that is supposed to mean. The postfix "stable" version is only updated approximately once a year. A program does not have to be updated every "X" number of days to be actively developed. In any case, there have been five new versions released since the one in the ports system was released. Certainly that would seem to indicate that something was happening with the application. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "clamav-unofficial-sigs" error message
On 2017-06-25 18:16, Carmel NY wrote: On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: From what I can see, the clamav-unofficial-sigs port works. It determines if there are updates or whether you have checked recently, so that you do not inadvertently dos the signature servers. What is NOT working, apparently, is clamav. Did you install clamav via ports? If it is installed, what is the clamscan_bin variable set to in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to be set to the correct path, for instance /usr/local/bin/clamscan. The correct path on your setup can be determined using 'which clamscan' From the "master.conf" file: # Custom Command Paths, these are detected with the which command when not set. Clamscan was commented out; however, the default setting was to /usr/bin/clamscan From what I can figure out, the "which" command worked fine outside of a CRON job, but was failing when clamav-unofficial-sigs.sh was run via CRON. I uncommented the "clamscan" setting and set it to point to the correct location. Now it works correctly. This is probably a bug, but I am not going to waste my time reporting it. The ports version of this program is very old. There have been five newer versions since its release. No doubt this problem has been corrected. The error message that you're getting has nothing to do with the version of the script that's available from the ports collection. Contrary to what you think, you would get the same error message with the latest version of the script (clamscan binary detection has remained exactly the same). You obviously did not set up PATH variable correctly for script invoking by cron daemon. On a side note, you mentioned that you edited "master.conf" file. As I wrote in pkg-message, all user configuration changes should go in file "user.conf" file, in order to make updating the script easier. As far as updating the port to the latest version is concerned, the development of the script appeared to be on halt since there were no updates from august last year until march this year and now it is quiet once again. The original script ended up being abandoned and I'm more cautious this time, so that I don't end up wasting my time. -- Regards, Marko Njezic - mr.maX @ MAX Interactive corp. Personal: http://www.markonjezic.com/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "clamav-unofficial-sigs" error message
On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: >From what I can see, the clamav-unofficial-sigs port works. It >determines if there are updates or whether you have checked recently, >so that you do not inadvertently dos the signature servers. What is >NOT working, apparently, is clamav. Did you install clamav via ports? >If it is installed, what is the clamscan_bin variable set to >in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to >be set to the correct path, for instance /usr/local/bin/clamscan. The >correct path on your setup can be determined using 'which clamscan' From the "master.conf" file: # Custom Command Paths, these are detected with the which command when not set. Clamscan was commented out; however, the default setting was to /usr/bin/clamscan From what I can figure out, the "which" command worked fine outside of a CRON job, but was failing when clamav-unofficial-sigs.sh was run via CRON. I uncommented the "clamscan" setting and set it to point to the correct location. Now it works correctly. This is probably a bug, but I am not going to waste my time reporting it. The ports version of this program is very old. There have been five newer versions since its release. No doubt this problem has been corrected. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "clamav-unofficial-sigs" error message
> Am 25.06.2017 um 12:24 schrieb Carmel NY <carmel...@outlook.com>: > > I recently installed clamav-unofficial-sigs via the ports system. The > port version is quite old,v5.3.2, while the current version is v5.6.2. > In any case, I am receiving the following error message repeatedly: > > Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found > > This is the full log from the last 12 hours or so: > > Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 16:38:57 Preparing Databases > Jun 24 16:38:58 Sanesecurity Database File Updates > Jun 24 16:38:58 2 hours have not yet elapsed since the last sanesecurity > update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 0 hour(s), 53 > minute(s) > Jun 24 16:38:58 SecuriteInfo Database File Updates > Jun 24 16:38:58 4 hours have not yet elapsed since the last SecuriteInfo > update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 2 hour(s), 53 > minute(s) > Jun 24 16:38:58 linuxmalwaredetect Database File Updates > Jun 24 16:38:58 6 hours have not yet elapsed since the last linux malware > detect update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 4 hour(s), 53 > minute(s) > Jun 24 16:38:58 MalwarePatrol Database File Update > Jun 24 16:38:58 24 hours have not yet elapsed since the last MalwarePatrol > download > Jun 24 16:38:58 No database download was performed at this time > Jun 24 16:38:58 Next download will be performed in approximately 22 hour(s), > 53 minute(s) > Jun 24 16:38:58 Setting permissions and ownership > Jun 24 16:38:58 No updates detected, ClamAV databases were not reloaded > Jun 24 16:38:58 Issue tracker : > https://github.com/extremeshok/clamav-unofficial-sigs/issues > Jun 24 16:38:59 New version : v5.6.2 @ > https://github.com/extremeshok/clamav-unofficial-sigs > Jun 24 16:38:59 Powered By https://eXtremeSHOK.com > Jun 24 16:41:07 Preparing Databases > Jun 24 16:41:08 Sanesecurity Database File Updates > Jun 24 16:41:08 2 hours have not yet elapsed since the last sanesecurity > update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 0 hour(s), 50 > minute(s) > Jun 24 16:41:08 SecuriteInfo Database File Updates > Jun 24 16:41:08 4 hours have not yet elapsed since the last SecuriteInfo > update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 2 hour(s), 50 > minute(s) > Jun 24 16:41:08 linuxmalwaredetect Database File Updates > Jun 24 16:41:08 6 hours have not yet elapsed since the last linux malware > detect update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 4 hour(s), 50 > minute(s) > Jun 24 16:41:08 MalwarePatrol Database File Update > Jun 24 16:41:08 24 hours have not yet elapsed since the last MalwarePatrol > download > Jun 24 16:41:08 No database download was performed at this time > Jun 24 16:41:08 Next download will be performed in approximately 22 hour(s), > 50 minute(s) > Jun 24 16:41:08 Setting permissions and ownership > Jun 24 16:41:08 No updates detected, ClamAV databases were not reloaded > Jun 24 16:41:08 Issue tracker : > https://github.com/extremeshok/clamav-unofficial-sigs/issues > Jun 24 16:41:08 New version : v5.6.2 @ > https://github.com/extremeshok/clamav-unofficial-sigs > Jun 24 16:41:08 Powered By https://eXtremeSHOK.com > Jun 24 16:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 17:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 18:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 19:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 20:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 21:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 22:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 23:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 00:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 01:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 02:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 03:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 04:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 05:45:00 ERROR: clamscan binary (clamscan_bin) not found >From what I can see, the clamav-unofficial-sigs port
"clamav-unofficial-sigs" error message
I recently installed clamav-unofficial-sigs via the ports system. The port version is quite old,v5.3.2, while the current version is v5.6.2. In any case, I am receiving the following error message repeatedly: Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found This is the full log from the last 12 hours or so: Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 16:38:57 Preparing Databases Jun 24 16:38:58 Sanesecurity Database File Updates Jun 24 16:38:58 2 hours have not yet elapsed since the last sanesecurity update check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 0 hour(s), 53 minute(s) Jun 24 16:38:58 SecuriteInfo Database File Updates Jun 24 16:38:58 4 hours have not yet elapsed since the last SecuriteInfo update check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 2 hour(s), 53 minute(s) Jun 24 16:38:58 linuxmalwaredetect Database File Updates Jun 24 16:38:58 6 hours have not yet elapsed since the last linux malware detect update check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 4 hour(s), 53 minute(s) Jun 24 16:38:58 MalwarePatrol Database File Update Jun 24 16:38:58 24 hours have not yet elapsed since the last MalwarePatrol download Jun 24 16:38:58 No database download was performed at this time Jun 24 16:38:58 Next download will be performed in approximately 22 hour(s), 53 minute(s) Jun 24 16:38:58 Setting permissions and ownership Jun 24 16:38:58 No updates detected, ClamAV databases were not reloaded Jun 24 16:38:58 Issue tracker : https://github.com/extremeshok/clamav-unofficial-sigs/issues Jun 24 16:38:59 New version : v5.6.2 @ https://github.com/extremeshok/clamav-unofficial-sigs Jun 24 16:38:59 Powered By https://eXtremeSHOK.com Jun 24 16:41:07 Preparing Databases Jun 24 16:41:08 Sanesecurity Database File Updates Jun 24 16:41:08 2 hours have not yet elapsed since the last sanesecurity update check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 0 hour(s), 50 minute(s) Jun 24 16:41:08 SecuriteInfo Database File Updates Jun 24 16:41:08 4 hours have not yet elapsed since the last SecuriteInfo update check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 2 hour(s), 50 minute(s) Jun 24 16:41:08 linuxmalwaredetect Database File Updates Jun 24 16:41:08 6 hours have not yet elapsed since the last linux malware detect update check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 4 hour(s), 50 minute(s) Jun 24 16:41:08 MalwarePatrol Database File Update Jun 24 16:41:08 24 hours have not yet elapsed since the last MalwarePatrol download Jun 24 16:41:08 No database download was performed at this time Jun 24 16:41:08 Next download will be performed in approximately 22 hour(s), 50 minute(s) Jun 24 16:41:08 Setting permissions and ownership Jun 24 16:41:08 No updates detected, ClamAV databases were not reloaded Jun 24 16:41:08 Issue tracker : https://github.com/extremeshok/clamav-unofficial-sigs/issues Jun 24 16:41:08 New version : v5.6.2 @ https://github.com/extremeshok/clamav-unofficial-sigs Jun 24 16:41:08 Powered By https://eXtremeSHOK.com Jun 24 16:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 17:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 18:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 19:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 20:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 21:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 22:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 23:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 00:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 01:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 02:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 03:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 04:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 05:45:00 ERROR: clamscan binary (clamscan_bin) not found I have no idea what the problem is. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav-unofficial-sigs
On Sun, 25 Jun 2017 09:49:09 +0200, Kurt Jaeger stated: >Hi! > >> The port version of "clamav-unofficial-sigs" is 5.3.2; however a >> newer version 5.6.2 is available. The port version is quite old. Are >> there any plans to update the port? > >Have you tried to provide a patch ? It's structure changed a little >bit, so it does not simply works in the ports framework. Could you elaborate on what "does not simply works in the ports framework" refers to? Thanks! -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav-unofficial-sigs
Hi! > The port version of "clamav-unofficial-sigs" is 5.3.2; however a newer > version 5.6.2 is available. The port version is quite old. Are there > any plans to update the port? Have you tried to provide a patch ? It's structure changed a little bit, so it does not simply works in the ports framework. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
clamav-unofficial-sigs
The port version of "clamav-unofficial-sigs" is 5.3.2; however a newer version 5.6.2 is available. The port version is quite old. Are there any plans to update the port? -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere: security/clamav fails due to deleted devel/llvm36
Is fixed now, thanks for the report. On Tue, May 02, 2017 at 09:14:52AM +0200, O. Hartmann wrote: > Someone/something messed up the ports tree: > > [00:00:22] >> Error: security/clamav depends on nonexistent origin > 'devel/llvm36'; Please contact maintainer of the port to fix this. [00:00:22] > ====>> Error: security/clamav-milter depends on nonexistent origin > 'devel/llvm36'; Please contact maintainer of the port to fix this. > > It seems some dependencies to deleted port devel/llvm36 are still active. > > Regrads, > Oliver > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
poudriere: security/clamav fails due to deleted devel/llvm36
Someone/something messed up the ports tree: [00:00:22] >> Error: security/clamav depends on nonexistent origin 'devel/llvm36'; Please contact maintainer of the port to fix this. [00:00:22] >> Error: security/clamav-milter depends on nonexistent origin 'devel/llvm36'; Please contact maintainer of the port to fix this. It seems some dependencies to deleted port devel/llvm36 are still active. Regrads, Oliver ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
Hi! > On Mon, 21 Mar 2016 14:30:25 -0700, Kevin Oberman stated: > > >Hmm. Let's see. A bug that may allow the defeat of a security > >mechanism and allow a black-hat to do bad stuff before the bug con > >even be looked at. Why would anyone have an issue with that? I mean, > >don't we all want more zero-day vulnerabilities? (Sorry, Guess I put > >on my sarcasm hat today.) > > You are right. Hell, if I had cancer why should the doctor tell me if > there is no cure for it. By the way, you must be a government employee. > You know, the type thats wants to keep everything secret but pry into > everyone else's life. The problem report is now public, btw. No need to get personal 8-) -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Mon, 21 Mar 2016 14:30:25 -0700, Kevin Oberman stated: >Hmm. Let's see. A bug that may allow the defeat of a security >mechanism and allow a black-hat to do bad stuff before the bug con >even be looked at. Why would anyone have an issue with that? I mean, >don't we all want more zero-day vulnerabilities? (Sorry, Guess I put >on my sarcasm hat today.) You are right. Hell, if I had cancer why should the doctor tell me if there is no cure for it. By the way, you must be a government employee. You know, the type thats wants to keep everything secret but pry into everyone else's life. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Sun, Mar 20, 2016 at 1:32 PM, Carmel <carmel...@outlook.com> wrote: > On Sun, 20 Mar 2016 16:42:54 +0100, Kurt Jaeger stated: > > >Hi! > > > >> >The make check of clamav exposes some issues, I've reported them > >> >upstream: > >> > > >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542 > >> > >> For whatever reason, I keep getting this error message when I try an > >> access that report: > >> > >> You are not authorized to access bug #11542. > > > >Yes. It seems clamav bugzilla is restrictive and I can not change > >that, as submitter of that bug. > > Now that makes about "ZERO" sense. Why would you (meaning clamav) want > to hide bug information? Dumbest thing I ever saw (almost). Hmm. Let's see. A bug that may allow the defeat of a security mechanism and allow a black-hat to do bad stuff before the bug con even be looked at. Why would anyone have an issue with that? I mean, don't we all want more zero-day vulnerabilities? (Sorry, Guess I put on my sarcasm hat today.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
Hi! > >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542 > >> > >> For whatever reason, I keep getting this error message when I try an > >> access that report: > >> > >> You are not authorized to access bug #11542. > >Yes. It seems clamav bugzilla is restrictive and I can not change > >that, as submitter of that bug. > > Now that makes about "ZERO" sense. Why would you (meaning clamav) want > to hide bug information? Dumbest thing I ever saw (almost). I added you to the Cc: for this bug, so that you can see it. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
Hi! > >Yes. It seems clamav bugzilla is restrictive and I can not change > >that, as submitter of that bug. > > Now that makes about "ZERO" sense. Why would you (meaning clamav) want > to hide bug information? Dumbest thing I ever saw (almost). There are several instances of ticket systems, where security relevant problem reports are kept restricted. Cisco does it, redhat does it, so... -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Sun, 20 Mar 2016 16:42:54 +0100, Kurt Jaeger stated: >Hi! > >> >The make check of clamav exposes some issues, I've reported them >> >upstream: >> > >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542 >> >> For whatever reason, I keep getting this error message when I try an >> access that report: >> >> You are not authorized to access bug #11542. > >Yes. It seems clamav bugzilla is restrictive and I can not change >that, as submitter of that bug. Now that makes about "ZERO" sense. Why would you (meaning clamav) want to hide bug information? Dumbest thing I ever saw (almost). -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
Hi! > >The make check of clamav exposes some issues, I've reported them > >upstream: > > > >https://bugzilla.clamav.net/show_bug.cgi?id=11542 > > For whatever reason, I keep getting this error message when I try an > access that report: > > You are not authorized to access bug #11542. Yes. It seems clamav bugzilla is restrictive and I can not change that, as submitter of that bug. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Sun, 20 Mar 2016 12:44:02 +0100, Kurt Jaeger stated: >The make check of clamav exposes some issues, I've reported them >upstream: > >https://bugzilla.clamav.net/show_bug.cgi?id=11542 For whatever reason, I keep getting this error message when I try an access that report: You are not authorized to access bug #11542. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
Hi! > >Do you have LLVM Enable JIT Bytecode compiler (bundled LLVM) enabled > >when you do build clamav ? If so try building without that. > >If I try to build with that enabled on amd64 current, the tests fail, > >without that enabled everything works fine > > Okay, disabling that option and rebuilding "clamav" cured the problem. > Maybe it should be turned off by default in the Makefile. The make check of clamav exposes some issues, I've reported them upstream: https://bugzilla.clamav.net/show_bug.cgi?id=11542 -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Sat, 19 Mar 2016 16:07:25 -0700, Manfred Antar stated: >Do you have LLVM Enable JIT Bytecode compiler (bundled LLVM) enabled >when you do build clamav ? If so try building without that. >If I try to build with that enabled on amd64 current, the tests fail, >without that enabled everything works fine Okay, disabling that option and rebuilding "clamav" cured the problem. Maybe it should be turned off by default in the Makefile. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
> On Mar 19, 2016, at 3:46 PM, Carmel <carmel...@outlook.com> wrote: > > On Sat, 19 Mar 2016 22:05:41 +0100, Dimitry Andric stated: > >> Probably, though the rest of the internet is reachable just fine. But >> that doesn't help me understand what the bug is. Can you please >> explain? > > It appears to be a problem with versions of LLVM greater than "3.6.2". > Freshclam crashes with this message: > > Received signal: wake up > ClamAV update process started at Sat Mar 19 17:24:14 2016 > main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: > amishhammer) > daily.cld is up to date (version: 21467, sigs: 83892, f-level: 63, builder: > amishhammer) > safebrowsing.cvd is up to date (version: 44501, sigs: 1935466, f-level: 63, > builder: google) > Downloading bytecode.cvd [100%] > ERROR: Database load killed by signal 11 > ERROR: Failed to load new database > > I am running FreeBSD 11 /amd64. I am not sure what version of LLVM I > have installed. > > -- > Carmel > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org” > Do you have LLVM Enable JIT Bytecode compiler (bundled LLVM) enabled when you do build clamav ? If so try building without that. If I try to build with that enabled on amd64 current, the tests fail, without that enabled everything works fine Manfred ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On Sat, 19 Mar 2016 22:05:41 +0100, Dimitry Andric stated: >Probably, though the rest of the internet is reachable just fine. But >that doesn't help me understand what the bug is. Can you please >explain? It appears to be a problem with versions of LLVM greater than "3.6.2". Freshclam crashes with this message: Received signal: wake up ClamAV update process started at Sat Mar 19 17:24:14 2016 main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: amishhammer) daily.cld is up to date (version: 21467, sigs: 83892, f-level: 63, builder: amishhammer) safebrowsing.cvd is up to date (version: 44501, sigs: 1935466, f-level: 63, builder: google) Downloading bytecode.cvd [100%] ERROR: Database load killed by signal 11 ERROR: Failed to load new database I am running FreeBSD 11 /amd64. I am not sure what version of LLVM I have installed. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On 19 Mar 2016, at 18:54, Carmel <carmel...@outlook.com> wrote: > > On Sat, 19 Mar 2016 17:18:17 +0100, Dimitry Andric stated: >> On 18 Mar 2016, at 20:09, Carmel <carmel...@outlook.com> wrote: >>> >>> On Fri, 18 Mar 2016 13:32:01 -0400, Michael Butler stated: >>>> On 03/18/16 13:17, Carmel wrote: >>>>> I have been bitten by this bug: >>>>> https://bugzilla.clamav.net/show_bug.cgi?id=11309 >>>>> >>>>> Is there anyway to correct it on a FreeBSD machine? I saw a few >>>>> suggestions, but they were not for this OS. >>>>> >>>> >>>> Oddly enough, recompiling with gcc-4.8 works :-( >>> >>> So, this is a "clang" problem? If I knew exactly what the problem >>> was, I would file a bug report with them. >> >> What is the actual bug? Apparently the clamav site is being DOS'd, or >> it is down, as the URL you mentioned above is unreachable. >> >> -Dimitry > > It is working fine here. It might be something on your end. Probably, though the rest of the internet is reachable just fine. But that doesn't help me understand what the bug is. Can you please explain? -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: clamav problem
On Sat, 19 Mar 2016 17:18:17 +0100, Dimitry Andric stated: >On 18 Mar 2016, at 20:09, Carmel <carmel...@outlook.com> wrote: >> >> On Fri, 18 Mar 2016 13:32:01 -0400, Michael Butler stated: >>> On 03/18/16 13:17, Carmel wrote: >>>> I have been bitten by this bug: >>>> https://bugzilla.clamav.net/show_bug.cgi?id=11309 >>>> >>>> Is there anyway to correct it on a FreeBSD machine? I saw a few >>>> suggestions, but they were not for this OS. >>>> >>> >>> Oddly enough, recompiling with gcc-4.8 works :-( >> >> So, this is a "clang" problem? If I knew exactly what the problem >> was, I would file a bug report with them. > >What is the actual bug? Apparently the clamav site is being DOS'd, or >it is down, as the URL you mentioned above is unreachable. > >-Dimitry It is working fine here. It might be something on your end. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On 18 Mar 2016, at 20:09, Carmel <carmel...@outlook.com> wrote: > > On Fri, 18 Mar 2016 13:32:01 -0400, Michael Butler stated: >> On 03/18/16 13:17, Carmel wrote: >>> I have been bitten by this bug: >>> https://bugzilla.clamav.net/show_bug.cgi?id=11309 >>> >>> Is there anyway to correct it on a FreeBSD machine? I saw a few >>> suggestions, but they were not for this OS. >>> >> >> Oddly enough, recompiling with gcc-4.8 works :-( > > So, this is a "clang" problem? If I knew exactly what the problem was, > I would file a bug report with them. What is the actual bug? Apparently the clamav site is being DOS'd, or it is down, as the URL you mentioned above is unreachable. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: clamav problem
On Fri, 18 Mar 2016 13:32:01 -0400, Michael Butler stated: >On 03/18/16 13:17, Carmel wrote: >> I have been bitten by this bug: >> https://bugzilla.clamav.net/show_bug.cgi?id=11309 >> >> Is there anyway to correct it on a FreeBSD machine? I saw a few >> suggestions, but they were not for this OS. >> > >Oddly enough, recompiling with gcc-4.8 works :-( So, this is a "clang" problem? If I knew exactly what the problem was, I would file a bug report with them. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
clamav problem
I have been bitten by this bug: https://bugzilla.clamav.net/show_bug.cgi?id=11309 Is there anyway to correct it on a FreeBSD machine? I saw a few suggestions, but they were not for this OS. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: clamav problem
On 03/18/16 13:17, Carmel wrote: > I have been bitten by this bug: > https://bugzilla.clamav.net/show_bug.cgi?id=11309 > > Is there anyway to correct it on a FreeBSD machine? I saw a few > suggestions, but they were not for this OS. > Oddly enough, recompiling with gcc-4.8 works :-( Michael ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Poudriere build of security/clamav-0.99 fails "check"
I was running poudriere (to build packages for tomorrow's weekly update of my "production" systems at home) on my build machine: FreeBSD freebeast.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #1878 r292113M/292127:1002502: Sat Dec 12 04:27:47 PST 2015 r...@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC amd64 and out of the 293 packages attempted, I had 2 failures; one of those was security/clamav-0.99 (updating from -0.98.7); last part of the log shows: ... ===> Returning to build of clamav-0.99 === === ... checking for timegm... yes checking for sysctlbyname... yes checking for pkg-config... no checking for CHECK... no checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking check.h usability... yes checking check.h presence... yes checking for check.h... yes checking linking with check... configure: unable to compile/link with check configure: error: ERROR! Check was configured, but not found. Get it from http://check.sf.net/ ===> Script "configure" failed unexpectedly. Please report the problem to ga...@freebsd.org [maintainer] and attach the "/wrkdirs/usr/ports/security/clamav/work/clamav-0.99/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /usr/ports/security/clamav >> Cleaning up wrkdir ===> Cleaning for clamav-0.99 >> Warning: Leftover processes: USER PID %CPU %MEM VSZ RSS TT STAT STARTEDTIME COMMAND build of security/clamav ended at Sat Dec 12 06:12:34 PST 2015 build time: 00:01:44 !!! build failure encountered !!! [end of build log -- dhw] A bit of searching the Net shows that others have encountered a similar condition, though I'm failing to find an actual resolution. Am I doing something silly, or does this warrant a PR? Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
ClamAV | Port update 0.99
Dear port maintainer, Can you tell me when the ClamAV 0.99 version will be released? Recently got a message when updating, saying: Local version: 0.98.7 Recommended version: 0.99 thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ClamAV
Dear port maintainer, Just ran into an update issue with the ClamAV port: --- cut --- ../libclamav/others.h:317: error: expected specifier-qualifier-list before 'clcb_file_props' ../libclamav/others.h:388: error: expected specifier-qualifier-list before 'clcb_file_props' ../shared/cdiff.c: In function 'cdiff_apply': ../shared/cdiff.c:781: error: 'EVP_MD_CTX' undeclared (first use in this function) ../shared/cdiff.c:781: error: (Each undeclared identifier is reported only once ../shared/cdiff.c:781: error: for each function it appears in.) ../shared/cdiff.c:781: error: 'sha256ctx' undeclared (first use in this function) Makefile:685: recipe for target 'cdiff.o' failed gmake[2]: *** [cdiff.o] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5/freshclam' Makefile:717: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5' Makefile:545: recipe for target 'all' failed gmake: *** [all] Error 2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/security/clamav. *** [build] Error code 1 Stop in /usr/ports/security/clamav. === make build failed for security/clamav === Aborting update === Update for security/clamav failed === Aborting update --- end --- Can you provide a solution for this? Thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV
I already filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182 On 2014-11-19 14:40, Jos Chrispijn wrote: Dear port maintainer, Just ran into an update issue with the ClamAV port: --- cut --- ../libclamav/others.h:317: error: expected specifier-qualifier-list before 'clcb_file_props' ../libclamav/others.h:388: error: expected specifier-qualifier-list before 'clcb_file_props' ../shared/cdiff.c: In function 'cdiff_apply': ../shared/cdiff.c:781: error: 'EVP_MD_CTX' undeclared (first use in this function) ../shared/cdiff.c:781: error: (Each undeclared identifier is reported only once ../shared/cdiff.c:781: error: for each function it appears in.) ../shared/cdiff.c:781: error: 'sha256ctx' undeclared (first use in this function) Makefile:685: recipe for target 'cdiff.o' failed gmake[2]: *** [cdiff.o] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5/freshclam' Makefile:717: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5' Makefile:545: recipe for target 'all' failed gmake: *** [all] Error 2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/security/clamav. *** [build] Error code 1 Stop in /usr/ports/security/clamav. === make build failed for security/clamav === Aborting update === Update for security/clamav failed === Aborting update --- end --- Can you provide a solution for this? Thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV
Hi! Just ran into an update issue with the ClamAV port: --- cut --- ../libclamav/others.h:317: error: expected specifier-qualifier-list before 'clcb_file_props' Can you deinstall the old before before building the new ? This sometimes happens with ports (they dont build if the older version is installed). See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193371 -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV
Larry Rosenman wrote on 19-11-2014: I already filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182 Thanks. Should I wait for an update or should I do a deinstall and reinstall to see if Kurt's suggestion works? BR, Jos Chrispijn On 2014-11-19 14:40, Jos Chrispijn wrote: Dear port maintainer, Just ran into an update issue with the ClamAV port: --- cut --- ../libclamav/others.h:317: error: expected specifier-qualifier-list before 'clcb_file_props' ../libclamav/others.h:388: error: expected specifier-qualifier-list before 'clcb_file_props' ../shared/cdiff.c: In function 'cdiff_apply': ../shared/cdiff.c:781: error: 'EVP_MD_CTX' undeclared (first use in this function) ../shared/cdiff.c:781: error: (Each undeclared identifier is reported only once ../shared/cdiff.c:781: error: for each function it appears in.) ../shared/cdiff.c:781: error: 'sha256ctx' undeclared (first use in this function) Makefile:685: recipe for target 'cdiff.o' failed gmake[2]: *** [cdiff.o] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5/freshclam' Makefile:717: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5' Makefile:545: recipe for target 'all' failed gmake: *** [all] Error 2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/security/clamav. *** [build] Error code 1 Stop in /usr/ports/security/clamav. === make build failed for security/clamav === Aborting update === Update for security/clamav failed === Aborting update --- end --- Can you provide a solution for this? Thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV
On 2014-11-19 14:49, Jos Chrispijn wrote: Larry Rosenman wrote on 19-11-2014: I already filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182 Thanks. Should I wait for an update or should I do a deinstall and reinstall to see if Kurt's suggestion works? I haven't tried that (and don't want to get into a situation where it's not on the system). Feel free to try and report back, and also add yourself to the CC list on the PR. BR, Jos Chrispijn On 2014-11-19 14:40, Jos Chrispijn wrote: Dear port maintainer, Just ran into an update issue with the ClamAV port: --- cut --- ../libclamav/others.h:317: error: expected specifier-qualifier-list before 'clcb_file_props' ../libclamav/others.h:388: error: expected specifier-qualifier-list before 'clcb_file_props' ../shared/cdiff.c: In function 'cdiff_apply': ../shared/cdiff.c:781: error: 'EVP_MD_CTX' undeclared (first use in this function) ../shared/cdiff.c:781: error: (Each undeclared identifier is reported only once ../shared/cdiff.c:781: error: for each function it appears in.) ../shared/cdiff.c:781: error: 'sha256ctx' undeclared (first use in this function) Makefile:685: recipe for target 'cdiff.o' failed gmake[2]: *** [cdiff.o] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5/freshclam' Makefile:717: recipe for target 'all-recursive' failed gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory '/usr/ports/security/clamav/work/clamav-0.98.5' Makefile:545: recipe for target 'all' failed gmake: *** [all] Error 2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/security/clamav. *** [build] Error code 1 Stop in /usr/ports/security/clamav. === make build failed for security/clamav === Aborting update === Update for security/clamav failed === Aborting update --- end --- Can you provide a solution for this? Thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV
Larry Rosenman wrote on 19-11-2014: On 2014-11-19 14:49, Jos Chrispijn wrote: Larry Rosenman wrote on 19-11-2014: I already filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195182 Thanks. Should I wait for an update or should I do a deinstall and reinstall to see if Kurt's suggestion works? I haven't tried that (and don't want to get into a situation where it's not on the system). Feel free to try and report back, and also add yourself to the CC list on the PR. Just deinstalled and installed and that worked for me. Thanks for your reply and the suggestion, Kurt. BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Sat, May 17, 2014 at 9:28 AM, Herbert J. Skuhra hsku...@eumx.net wrote: On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. Hey Herbert, Applying this patch will fix the issue: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 Renato, can you please add that patch to the port? Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Sat, 17 May 2014 10:35:55 -0400 Shawn Webb wrote: On Sat, May 17, 2014 at 9:28 AM, Herbert J. Skuhra hsku...@eumx.net wrote: On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. Hey Herbert, Applying this patch will fix the issue: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 Renato, can you please add that patch to the port? OK, this has been added in r354178. No idea why I still got this error in clamav-0.98.3_3. After rebuilding the port once more the error is gone. Thanks. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unable to update to clamav 0.98.3
On 05/13/14 11:55, Jerry wrote: On Mon, 12 May 2014 11:03:50 -0300, Renato Botelho stated: On Thursday, May 08, 2014 04:35:11 PM Jerry wrote: FreeBSD 10.0-RELEASE I am unable to update to clamav-0.98.3. It terminates with the following error message: clamd.c:335:59: warning: format specifies type 'unsigned int' but the argument has type 'off_t' (aka 'long') [-Wformat] logg(#Log file size limited to %u bytes.\n, logg_size); ~~^ %ld 1 warning generated. CC tcpserver.o CC localserver.o CC session.o CC thrmgr.o CC server-th.o CC scanner.o scanner.c:105:25: warning: passing 'const unsigned char *' to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign] strncpy(c-virhash, md5, 32); ^~~ /usr/include/string.h:101:57: note: passing argument to parameter here char*strncpy(char * __restrict, const char * __restrict, size_t); ^ 1 warning generated. CC others.o CC fan.o CCLD clamd gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in clamdscan gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC output.o CC optparser.o CC misc.o CC getopt.o CC actions.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC clamdscan.o CC proto.o CC client.o CCLD clamdscan gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in freshclam gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC output.o CC optparser.o CC getopt.o CC misc.o CC cdiff.o CC tar.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC freshclam.o In file included from freshclam.c:57: In file included from ../libclamav/others.h:21: In file included from ../libclamav/matcher.h:28: ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t' stats_section_t *sections; ^ ../libclamav/others.h:323:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:324:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:325:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:326:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:327:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:328:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:329:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:330:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ ../libclamav/others.h:380:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:381:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:382:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:385:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:386:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:387:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ freshclam.c:762:5: warning: implicit declaration of function
Re: Unable to update to clamav 0.98.3
On Tuesday, May 13, 2014 05:55:04 AM Jerry wrote: On Mon, 12 May 2014 11:03:50 -0300, Renato Botelho stated: On Thursday, May 08, 2014 04:35:11 PM Jerry wrote: FreeBSD 10.0-RELEASE I am unable to update to clamav-0.98.3. It terminates with the following error message: clamd.c:335:59: warning: format specifies type 'unsigned int' but the argument has type 'off_t' (aka 'long') [-Wformat] logg(#Log file size limited to %u bytes.\n, logg_size); ~~^ %ld 1 warning generated. CC tcpserver.o CC localserver.o CC session.o CC thrmgr.o CC server-th.o CC scanner.o scanner.c:105:25: warning: passing 'const unsigned char *' to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign] strncpy(c-virhash, md5, 32); ^~~ /usr/include/string.h:101:57: note: passing argument to parameter here char*strncpy(char * __restrict, const char * __restrict, size_t); ^ 1 warning generated. CC others.o CC fan.o CCLD clamd gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in clamdscan gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC output.o CC optparser.o CC misc.o CC getopt.o CC actions.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC clamdscan.o CC proto.o CC client.o CCLD clamdscan gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in freshclam gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC output.o CC optparser.o CC getopt.o CC misc.o CC cdiff.o CC tar.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC freshclam.o In file included from freshclam.c:57: In file included from ../libclamav/others.h:21: In file included from ../libclamav/matcher.h:28: ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t' stats_section_t *sections; ^ ../libclamav/others.h:323:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:324:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:325:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:326:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:327:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:328:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:329:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:330:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ ../libclamav/others.h:380:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:381:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:382:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush
clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Thu, May 15, 2014 at 5:20 PM, Dr. Peter Voigt pvo...@uos.de wrote: Am Thu, 15 May 2014 16:23:28 -0400 schrieb Shawn Webb latt...@gmail.com: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Thanks, Shawn Shawn, thanks for your extremely quick reply. I am afraid, I am not yet experienced enough to apply a patch to files of a port that are not permanently present in the ports tree like configure and m4/reorganization/version.m4. Nevertheless, the issue is obviously ClamAV related and should be merged to a new version of security/clamav. Should I open a corresponding PR or does the CC-ed maintainer feel informed sufficiently? Regards, Peter Opening a PR never hurts. I'm sure Renato will see both. As you can see by the link I provided, the fix for this is in upstream ClamAV 0.98.4, which will be released in the near future (sorry, no exact ETA). Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
Am Thu, 15 May 2014 16:23:28 -0400 schrieb Shawn Webb latt...@gmail.com: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Thanks, Shawn Shawn, thanks for your extremely quick reply. I am afraid, I am not yet experienced enough to apply a patch to files of a port that are not permanently present in the ports tree like configure and m4/reorganization/version.m4. Nevertheless, the issue is obviously ClamAV related and should be merged to a new version of security/clamav. Should I open a corresponding PR or does the CC-ed maintainer feel informed sufficiently? Regards, Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! -- Renato Botelho garga @ FreeBSD.org garga.bsd @ gmail.com GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unable to update to clamav 0.98.3
On Thu, 15 May 2014 07:33:01 -0400, Renato Botelho stated: Do you remember what was the version you had installed when tried to build the new version? I'm still trying to reproduce the issue to be able It was the latest version available before this new one was released. -- Jerry ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. Regards, Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unable to update to clamav 0.98.3
On Mon, 12 May 2014 11:03:50 -0300, Renato Botelho stated: On Thursday, May 08, 2014 04:35:11 PM Jerry wrote: FreeBSD 10.0-RELEASE I am unable to update to clamav-0.98.3. It terminates with the following error message: clamd.c:335:59: warning: format specifies type 'unsigned int' but the argument has type 'off_t' (aka 'long') [-Wformat] logg(#Log file size limited to %u bytes.\n, logg_size); ~~^ %ld 1 warning generated. CC tcpserver.o CC localserver.o CC session.o CC thrmgr.o CC server-th.o CC scanner.o scanner.c:105:25: warning: passing 'const unsigned char *' to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign] strncpy(c-virhash, md5, 32); ^~~ /usr/include/string.h:101:57: note: passing argument to parameter here char*strncpy(char * __restrict, const char * __restrict, size_t); ^ 1 warning generated. CC others.o CC fan.o CCLD clamd gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in clamdscan gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC output.o CC optparser.o CC misc.o CC getopt.o CC actions.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC clamdscan.o CC proto.o CC client.o CCLD clamdscan gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in freshclam gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC output.o CC optparser.o CC getopt.o CC misc.o CC cdiff.o CC tar.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC freshclam.o In file included from freshclam.c:57: In file included from ../libclamav/others.h:21: In file included from ../libclamav/matcher.h:28: ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t' stats_section_t *sections; ^ ../libclamav/others.h:323:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:324:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:325:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:326:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:327:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:328:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:329:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:330:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ ../libclamav/others.h:380:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:381:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:382:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:385:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:386:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:387:5: error: unknown
Re: Unable to update to clamav 0.98.3
On Thursday, May 08, 2014 04:35:11 PM Jerry wrote: FreeBSD 10.0-RELEASE I am unable to update to clamav-0.98.3. It terminates with the following error message: clamd.c:335:59: warning: format specifies type 'unsigned int' but the argument has type 'off_t' (aka 'long') [-Wformat] logg(#Log file size limited to %u bytes.\n, logg_size); ~~^ %ld 1 warning generated. CC tcpserver.o CC localserver.o CC session.o CC thrmgr.o CC server-th.o CC scanner.o scanner.c:105:25: warning: passing 'const unsigned char *' to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign] strncpy(c-virhash, md5, 32); ^~~ /usr/include/string.h:101:57: note: passing argument to parameter here char*strncpy(char * __restrict, const char * __restrict, size_t); ^ 1 warning generated. CC others.o CC fan.o CCLD clamd gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in clamdscan gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC output.o CC optparser.o CC misc.o CC getopt.o CC actions.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC clamdscan.o CC proto.o CC client.o CCLD clamdscan gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in freshclam gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC output.o CC optparser.o CC getopt.o CC misc.o CC cdiff.o CC tar.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC freshclam.o In file included from freshclam.c:57: In file included from ../libclamav/others.h:21: In file included from ../libclamav/matcher.h:28: ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t' stats_section_t *sections; ^ ../libclamav/others.h:323:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:324:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:325:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:326:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:327:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:328:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:329:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:330:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ ../libclamav/others.h:380:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:381:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:382:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:385:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:386:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:387:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ freshclam.c:762:5: warning: implicit declaration
Re: problem with clamav
On Sun, 24 Nov 2013, Dewayne Geraghty wrote: Thanks to Gerald for addressing this issue per http://svnweb.freebsd.org/ports/head/Mk/bsd.gcc.mk?sortby=dateview=log clamav now builds. Thanks for the confirmation. And sorry for the temporary breakage. Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: problem with clamav
On 23/11/2013 1:56 PM, Shawn Webb wrote: On Fri, Nov 22, 2013 at 8:57 PM, AN a...@neu.net wrote: FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. The problem wouldn't be with ClamAV, but with the port entry. ClamAV currently doesn't build with clang on 11-CURRENT, but it does indeed work with gcc (I'm building manually from source checked out via git, and am using gcc/g++ 4.6.4 from ports). Maybe the port maintainer has some input. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Unfortunately, I have the same problem on 9.2Stable (built/installed today), using default gcc only. cd /usr/ports/security/clamav make -DBATCH package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [all] Error code 1 Stop in /usr/ports/security/clamav. And the Makefile contains the line: USE_GCC=any The only reference to gcc in make.conf is: FAVORITE_COMPILER=gcc And for completeness # cd /usr/ports/security/clamav/ make -DBATCH __MAKE_CONF=/dev/null package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [package] Error code 1 Stop in /usr/ports/security/clamav. and # gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] Advice welcome? Regards, Dewayne. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: problem with clamav
On 24/11/2013 12:13 AM, Dewayne Geraghty wrote: On 23/11/2013 1:56 PM, Shawn Webb wrote: On Fri, Nov 22, 2013 at 8:57 PM, AN a...@neu.net wrote: FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. The problem wouldn't be with ClamAV, but with the port entry. ClamAV currently doesn't build with clang on 11-CURRENT, but it does indeed work with gcc (I'm building manually from source checked out via git, and am using gcc/g++ 4.6.4 from ports). Maybe the port maintainer has some input. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Unfortunately, I have the same problem on 9.2Stable (built/installed today), using default gcc only. cd /usr/ports/security/clamav make -DBATCH package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [all] Error code 1 Stop in /usr/ports/security/clamav. And the Makefile contains the line: USE_GCC=any The only reference to gcc in make.conf is: FAVORITE_COMPILER=gcc And for completeness # cd /usr/ports/security/clamav/ make -DBATCH __MAKE_CONF=/dev/null package === clamav-0.98_2 Unknown version of GCC specified (USE_GCC=any). *** [package] Error code 1 Stop in /usr/ports/security/clamav. and # gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] Advice welcome? Regards, Dewayne. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Thanks to Gerald for addressing this issue per http://svnweb.freebsd.org/ports/head/Mk/bsd.gcc.mk?sortby=dateview=log clamav now builds. Regards, Dewayne ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
problem with clamav
FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: problem with clamav
On Fri, Nov 22, 2013 at 8:57 PM, AN a...@neu.net wrote: FreeBSD .rootbsd.net 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r258260M: Sun Nov 17 13:01:19 EST 2013 rootbsd.net:/usr/obj/usr/src/sys/GENERIC amd64 # portupgrade -va --- Session started at: Fri, 22 Nov 2013 20:46:56 -0500 [Reading data from pkg(8) ... - 81 packages found - done] ** Port marked as IGNORE: security/clamav: Unknown version of GCC specified (USE_GCC=any) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - security/clamav (marked as IGNORE) --- Packages processed: 0 done, 1 ignored, 0 skipped and 0 failed --- Session ended at: Fri, 22 Nov 2013 20:47:00 -0500 (consumed 00:00:03) # pkg info |grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java # pkg info |grep clam clamav-0.98_2 Command line virus scanner written entirely in C Is clamav broken on current? Any suggestions on how to proceed? Thanks in advance. The problem wouldn't be with ClamAV, but with the port entry. ClamAV currently doesn't build with clang on 11-CURRENT, but it does indeed work with gcc (I'm building manually from source checked out via git, and am using gcc/g++ 4.6.4 from ports). Maybe the port maintainer has some input. Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: amavisd-new-2.8.0_2, 1 Re: Typo is amavisd.conf prevents startup if using ClamAV
Hello, not sure if anybody has mentioned this yet but in
/usr/local/etc/amavisd.conf in the ClamAV section
/var/run/clamav/clamd.sock.sock should be /var/run/clamav/clamd.sock
otherwise Amavis will not be able to start.
# ### http://www.clamav.net/
['ClamAV-clamd',
\ask_daemon, [CONTSCAN {}\n, /var/run/clamav/clamd.sock.sock],
qr/\bOK$/m, qr/\bFOUND$/m,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
Thanks and great port!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: amavisd-new-2.8.0_2, 1 Re: Typo is amavisd.conf prevents startup if using ClamAV
On Sat, 12 Jan 2013 10:17:11 -0800
Tay t...@taypop.com wrote:
Hello, not sure if anybody has mentioned this yet but in
/usr/local/etc/amavisd.conf in the ClamAV section
/var/run/clamav/clamd.sock.sock should be
/var/run/clamav/clamd.sock otherwise Amavis will not be able to
start.
# ### http://www.clamav.net/
['ClamAV-clamd',
\ask_daemon, [CONTSCAN {}\n, /var/run/clamav/clamd.sock.sock],
qr/\bOK$/m, qr/\bFOUND$/m,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
The amavisd.conf that ships with amavisd-new 2.8.0 does not contain
the wrong line.
% curl -O http://www.ijs.si/software/amavisd/amavisd-new-2.8.0.tar.gz
% tar xfvz amavisd-new-2.8.0.tar.gz
% cd amavisd-new-2.8.0
% grep clamd.sock amavisd.conf
# \ask_daemon, [CONTSCAN {}\n, /var/run/clamav/clamd.sock],
# \ask_daemon, [*, 'clamd:/var/run/clamav/clamd.sock'],
Maybe this comes from a previous version or a local problem.
--
Herbert
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV fetch error | SOLVED
Issue solved with processing port update clamav-0.97.3_1 BR, Jos Chrispijn Jos Chrispijn: Just updated my ports, got an unexpected error: = Attempting to fetch http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz fetch: http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz: size mismatch: expected 45793424, actual 45793398 can someone tell me how to solve this? Thanks. BR Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
clamav size mismatch: expected 45793424, actual 45793398
Any ideas? :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav size mismatch: expected 45793424, actual 45793398
## Doug Barton (do...@freebsd.org): Any ideas? :) Looks as if the official distfile really has 45793398 bytes. At least that's what I'm getting from from Sourceforge, and it's signed with the usual (i.e. used for previous releases) gpg key. Perhaps the clamav team rerolled their tarball at the time of the announcement? Given that I saw 0.97.3 in the ports tree before the announcement (from the clamav team) was in my mailbox... Regards, Christoph -- Spare Space ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
ClamAV fetch error
Just updated my ports, got an unexpected error: = Attempting to fetch http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz fetch: http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz: size mismatch: expected 45793424, actual 45793398 can someone tell me how to solve this? Thanks. BR Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV fetch error
Jos Chrispijn schreef: Just updated my ports, got an unexpected error: = Attempting to fetch http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz fetch: http://waix.dl.sourceforge.net/project/clamav/clamav/0.97.3/clamav-0.97.3.tar.gz: size mismatch: expected 45793424, actual 45793398 can someone tell me how to solve this? Thanks. BR Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Download clamav-0.97.3.tar.gz manually and place it in /usr/ports/distfiles. Then go to /usr/ports/security/clamav Then run make makesum from that directory. It will create a new distinfo file. But why is there a mismatch.?? Why is the version on the net different than the first tarball send to the port maintainer. Call me paranoia, but i do not trust this so i wait till things get cleared. :D regards Johan Hendriks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ClamAV fetch error
Johan Hendriks: But why is there a mismatch.?? Why is the version on the net different than the first tarball send to the port maintainer. Call me paranoia, but i do not trust this so i wait till things get cleared. :D So true; I will wait for clearing as well. Thanks for explaining; I found some information on disabeling the filesize compare, but I think that might cause a security issue as well. BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
