Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Frans,

Yes sorry haven't fixed the clamd test symlink issue yet. It's next on my to-do 
list. It will be fixed before we publish RC2.

Regards,
Micah

Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.

From: clamav-users  on behalf of Frans 
de Boer 
Sent: Friday, August 6, 2021 1:07 PM
To: clamav-users@lists.clamav.net 
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
here!

On 7/22/21 6:18 PM, Joel Esler (jesler) via clamav-users wrote:


https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html

ClamAV 0.104.0 Release Candidate is here!

We are pleased to announce the ClamAV 0.104.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>, or on our 
Discord<https://discord.gg/sGaxA5Q>, which is bridged with our IRC.

This release candidate phase is only expected to last about two to four weeks 
before the 0.104.0 Stable version will be published. Take this opportunity to 
verify that you 0.104.0 can build and run in your environment.

Please submit bug reports to the ClamAV project GitHub 
Issues<https://github.com/Cisco-Talos/clamav/issues>.

ClamAV 0.104.0 includes the following improvements and changes.

New Requirements

  *   As of ClamAV 0.104, CMake is required to build ClamAV.

  *   We have added comprehensive build instructions for using CMake to the new 
INSTALL.md file. The online documentation will also be updated to include CMake 
build instructions.
  *   The Autotools and the Visual Studio build systems have been removed.

Major changes

  *   The built-in LLVM for the bytecode runtime has been removed.

  *   The bytecode interpreter is the default runtime for bytecode signatures 
just as it was in ClamAV 0.103.
  *   We wished to add support for newer versions of LLVM, but ran out of time. 
If you're building ClamAV from source and you wish to use LLVM instead of the 
bytecode interpreter, you will need to supply the development libraries for 
LLVM version 3.6.2. See INSTALL.md to learn more.
  *   There are now official ClamAV images on Docker Hub.

 *   Note: Until ClamAV 0.104.0 is released, these images are limited to 
"unstable" versions, which are updated daily with the latest changes in the 
default branch on GitHub.

You can find the images on Docker Hub under 
clamav<https://hub.docker.com/r/clamav/clamav>.

Docker Hub ClamAV tags:

  *   clamav/clamav:: A release preloaded with signature databases.

Using this container will save the ClamAV project some bandwidth. Use this if 
you will keep the image around so that you don't download the entire database 
set every time you start a new container. Updating with FreshClam from the 
existing databases set does not use much data.

  *   clamav/clamav:_base: A release with no signature databases.

Use this container only if you mount a volume in your container under 
/var/lib/clamav to persist your signature database databases. This method is 
the best option because it will reduce data costs for ClamAV and for the Docker 
registry, but it does require advanced familiarity with Linux and Docker.

Caution: Using this image without mounting an existing database directory will 
cause FreshClam to download the entire database set each time you start a new 
container.

You can use the unstable version (i.e. clamav/clamav:unstable or 
clamav/clamav:unstable_base) to try the latest from our development branch.

Please, be kind when using "free" bandwidth for the virus databases and Docker 
registry. Try not to download the entire database set or the larger ClamAV 
database images on a regular basis.

For more details, see the ClamAV Docker 
documentation<https://docs.clamav.net/manual/Installing/Docker.html>.

Special thanks to Olliver Schinagl for his excellent work creating ClamAV's new 
Docker files, image database deployment tooling, and user documentation.

  *   clamd and freshclam are now available as Windows services. To install and 
run them, use the --install-service option and net start [name] command.

Special thanks to Gianluigi Tiesi for his original work on this feature.

Notable changes

We added these features in 0.103.1 but wanted to re-post them here, as patch 
versions do not generally introduce new options:

  *   Added a new scan option to alert on broken media (graphics) file formats. 
This feature mitigates the risk of malformed media files intended to exploit 
vulnerabilities in other software. Currently, media validation exists for JPEG, 
TIFF, PNG, and GIF files. To enable this feature, set AlertBrokenMedia yes in 
clamd.conf, or use the --alert-broken-media option when using clamscan. These 
options are disabled by default in this patch, but may be enabled in a 
subsequent rel

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

On 7/22/21 6:18 PM, Joel Esler (jesler) via clamav-users wrote:




https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html 




  ClamAV 0.104.0 Release Candidate is here!

We are pleased to announce the ClamAV 0.104.0 release candidate 
.


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 
, or on our 
Discord , which is bridged with our IRC.


This release candidate phase is only expected to last about two to 
four weeks before the 0.104.0 Stable version will be published. Take 
this opportunity to verify that you 0.104.0 can build and run in your 
environment.


Please submit bug reports to the ClamAV project GitHub Issues 
.


ClamAV 0.104.0 includes the following improvements and changes.


  New Requirements

 *

As of ClamAV 0.104, CMake is required to build ClamAV.

  * We have added comprehensive build instructions for using CMake to
the new |INSTALL.md| file. The online documentation will also be
updated to include CMake build instructions.
  * The Autotools and the Visual Studio build systems have been removed.


  Major changes

 *

The built-in LLVM for the bytecode runtime has been removed.

  * The bytecode interpreter is the default runtime for bytecode
signatures just as it was in ClamAV 0.103.
  * We wished to add support for newer versions of LLVM, but ran out
of time. If you're building ClamAV from source and you wish to
use LLVM instead of the bytecode interpreter, you will need to
supply the development libraries for LLVM version 3.6.2. See
|INSTALL.md| to learn more.
 *

There are now official ClamAV images on Docker Hub.

  o /Note/: Until ClamAV 0.104.0 is released, these images are
limited to "unstable" versions, which are updated daily with
the latest changes in the default branch on GitHub.

You can find the images on Docker Hub under |clamav| 
.


Docker Hub ClamAV tags:

 *

|clamav/clamav:|: A release preloaded with signature
databases.

Using this container will save the ClamAV project some bandwidth.
Use this if you will keep the image around so that you don't
download the entire database set every time you start a new
container. Updating with FreshClam from the existing databases
set does not use much data.

 *

|clamav/clamav:_base|: A release with no signature
databases.

Use this container *only* if you mount a volume in your container
under |/var/lib/clamav| to persist your signature database
databases. This method is the best option because it will reduce
data costs for ClamAV and for the Docker registry, but it does
require advanced familiarity with Linux and Docker.

/Caution/: Using this image without mounting an existing
database directory will cause FreshClam to download the
entire database set each time you start a new container.

You can use the |unstable| version (i.e. |clamav/clamav:unstable| or 
|clamav/clamav:unstable_base|) to try the latest from our development 
branch.


Please, be kind when using "free" bandwidth for the virus databases 
and Docker registry. Try not to download the entire database set or 
the larger ClamAV database images on a regular basis.


For more details, see the ClamAV Docker documentation 
.


Special thanks to Olliver Schinagl for his excellent work creating 
ClamAV's new Docker files, image database deployment tooling, and 
user documentation.


 *

|clamd| and |freshclam| are now available as Windows services. To
install and run them, use the |--install-service| option and |net
start [name]| command.

Special thanks to Gianluigi Tiesi for his original work on this
feature.


  Notable changes

We added these features in 0.103.1 but wanted to re-post them here, 
as patch versions do not generally introduce new options:


 *

Added a new scan option to alert on broken media (graphics) file
formats. This feature mitigates the risk of malformed media files
intended to exploit vulnerabilities in other software. Currently,
media validation exists for JPEG, TIFF, PNG, and GIF files. To
enable this feature, set |AlertBrokenMedia yes| in clamd.conf, or
use the |--alert-broken-media| option when using |clamscan|.
These options are disabled by default in this patch, but may be
enabled in a subsequent release. Application developers may
enable this scan option by enabling
|CL_SCAN_HEURISTIC_BROKEN_MEDIA| for the |heuristic| scan option
bit field.

 *

Added CL_TYPE_TIFF, CL_TYPE_JPEG types 

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

The option for setting the curses library and include directories are:
  -D CURSES_INCLUDE_DIR="_path to curses header directory_"
  -D CURSES_LIBRARY="_filepath of curses library_"

Your command had NCURSES_INCLUDE_DIR instead of CURSES_INCLUDE_DIR.

Also, it's great to hear that Mark's fix for the format string macros fixed 
things for you.  His patches were merged yesterday, here: 
https://github.com/Cisco-Talos/clamav/pull/231, so the second release candidate 
should have that issue resolved.

Regards,
Micah



Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.

From: clamav-users  on behalf of Andrew 
Watkins via clamav-users 
Sent: Friday, August 6, 2021 5:14 AM
To: clamav-users@lists.clamav.net ; h...@hege.li 

Cc: Andrew Watkins 
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
here!


On 05/08/2021 10:53, Henrik K wrote:
> On Sat, Jul 24, 2021 at 08:17:19PM +, Micah Snyder (micasnyd) via 
> clamav-users wrote:
>
> No problems on Solaris 11.4.32.0.1.88.3 (SPARC) here with latest fixes,
> 0.104 actually works stable and fast so far.  Some more ancient versions
> just kept crashing and were sloow (then again older Solaris versions had
> ancient gcc etc).
>
> Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) and
> other libraries (curl 7.71 etc).  All requirements except libcheck are OS
> provided, just pkg install them.
>
> Only thing that needed some manual fixing was some curses paths.
>
> mkdir build
> cd build
> cmake .. \
>-D CMAKE_BUILD_TYPE="Release" \
>-D ENABLE_TESTS=OFF \
>-D PCRE2_INCLUDE_DIR=/usr/include/pcre \
>-D NCURSES_INCLUDE_DIR=/usr/include/ncurses \
>-D CURSES_LIBRARY=/usr/lib/64/libncurses.so
>
> # Seems NCURSES_INCLUDE_DIR isn't used here..
> sed -i 's###' clamav-config.h

Thanks I tried the above it worked, but failed to build. Any ideas?

$ cmake --build .  --config Release
[ 13%] Linking CXX shared library libclamunrar.so
[ 13%] Built target clamunrar
Scanning dependencies of target unrar_iface_obj
[ 14%] Building CXX object
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/unrar_iface.cpp.o
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:
In function 'cl_unrar_error_t libceader(void*, unrar_metadata_t*)':
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:349:62:
error: expected ')' before
   349 | unrar_dbgmsg("unrar_peek_file_header:   Packed Size: %"
PRIu64 "\n", file_metadata->pack_size)
   | ~^
|  )
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:350:62:
error: expected ')' before
   350 | unrar_dbgmsg("unrar_peek_file_header:   Unpacked Size: %"
PRIu64 "\n", file_metadata->unpack_siz
   | ~^
|  )
gmake[2]: ***
[libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/build.make:63:
libclamunrar_iface/CMakeFilep.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1062:
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/all] Error 2
gmake: *** [Makefile:163: all] Error 2

Thanks

--

**
 At home during the crisis trying to work 
**
   Support Request to s...@dcs.bbk.ac.uk
**
Andrew Watkins * Birkbeck, University of London * Computer Science *
* http://notallmicrosoft.blogspot.com *
::e-mails are only read & actioned between 0900 and 1730 hours (Monday - Friday)


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Andrew Watkins via clamav-users]

On 06/08/2021 14:59, Mark Fortescue via clamav-users wrote:

Hi Andrew,

I have placed two patches on the user list that I believe may fix the 
issue you are seeing. I was seeing a similar issue hence the 
investigation and resulting patches.


https://www.mail-archive.com/clamav-users@lists.clamav.net/msg50910.html

and

ttps://www.mail-archive.com/clamav-users@lists.clamav.net/msg50957.html

Regards
Mark. 


Patches worked like a dream!

Thanks

Andrew


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi Andrew,

I have placed two patches on the user list that I believe may fix the 
issue you are seeing. I was seeing a similar issue hence the 
investigation and resulting patches.


https://www.mail-archive.com/clamav-users@lists.clamav.net/msg50910.html

and

ttps://www.mail-archive.com/clamav-users@lists.clamav.net/msg50957.html

Regards
Mark.

On 06/08/2021 10:14, Andrew Watkins via clamav-users wrote:


On 05/08/2021 10:53, Henrik K wrote:
On Sat, Jul 24, 2021 at 08:17:19PM +, Micah Snyder (micasnyd) via 
clamav-users wrote:


No problems on Solaris 11.4.32.0.1.88.3 (SPARC) here with latest fixes,
0.104 actually works stable and fast so far.  Some more ancient versions
just kept crashing and were sloow (then again older Solaris versions had
ancient gcc etc).

Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) 
and

other libraries (curl 7.71 etc).  All requirements except libcheck are OS
provided, just pkg install them.

Only thing that needed some manual fixing was some curses paths.

mkdir build
cd build
cmake .. \
   -D CMAKE_BUILD_TYPE="Release" \
   -D ENABLE_TESTS=OFF \
   -D PCRE2_INCLUDE_DIR=/usr/include/pcre \
   -D NCURSES_INCLUDE_DIR=/usr/include/ncurses \
   -D CURSES_LIBRARY=/usr/lib/64/libncurses.so

# Seems NCURSES_INCLUDE_DIR isn't used here..
sed -i 's###' clamav-config.h


Thanks I tried the above it worked, but failed to build. Any ideas?

$ cmake --build .  --config Release
[ 13%] Linking CXX shared library libclamunrar.so
[ 13%] Built target clamunrar
Scanning dependencies of target unrar_iface_obj
[ 14%] Building CXX object 
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/unrar_iface.cpp.o
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp: In 
function 'cl_unrar_error_t libceader(void*, unrar_metadata_t*)':
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:349:62: 
error: expected ')' before
   349 | unrar_dbgmsg("unrar_peek_file_header:   Packed Size: %" 
PRIu64 "\n", file_metadata->pack_size)

   | ~    ^
|  )
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:350:62: 
error: expected ')' before
   350 | unrar_dbgmsg("unrar_peek_file_header:   Unpacked Size: %" 
PRIu64 "\n", file_metadata->unpack_siz

   | ~    ^
|  )
gmake[2]: *** 
[libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/build.make:63: 
libclamunrar_iface/CMakeFilep.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1062: 
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/all] Error 2

gmake: *** [Makefile:163: all] Error 2

Thanks



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Andrew Watkins via clamav-users]

On 05/08/2021 10:53, Henrik K wrote:

On Sat, Jul 24, 2021 at 08:17:19PM +, Micah Snyder (micasnyd) via 
clamav-users wrote:

No problems on Solaris 11.4.32.0.1.88.3 (SPARC) here with latest fixes,
0.104 actually works stable and fast so far.  Some more ancient versions
just kept crashing and were sloow (then again older Solaris versions had
ancient gcc etc).

Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) and
other libraries (curl 7.71 etc).  All requirements except libcheck are OS
provided, just pkg install them.

Only thing that needed some manual fixing was some curses paths.

mkdir build
cd build
cmake .. \
   -D CMAKE_BUILD_TYPE="Release" \
   -D ENABLE_TESTS=OFF \
   -D PCRE2_INCLUDE_DIR=/usr/include/pcre \
   -D NCURSES_INCLUDE_DIR=/usr/include/ncurses \
   -D CURSES_LIBRARY=/usr/lib/64/libncurses.so

# Seems NCURSES_INCLUDE_DIR isn't used here..
sed -i 's###' clamav-config.h


Thanks I tried the above it worked, but failed to build. Any ideas?

$ cmake --build .  --config Release
[ 13%] Linking CXX shared library libclamunrar.so
[ 13%] Built target clamunrar
Scanning dependencies of target unrar_iface_obj
[ 14%] Building CXX object 
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/unrar_iface.cpp.o
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp: 
In function 'cl_unrar_error_t libceader(void*, unrar_metadata_t*)':
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:349:62: 
error: expected ')' before
  349 | unrar_dbgmsg("unrar_peek_file_header:   Packed Size: %" 
PRIu64 "\n", file_metadata->pack_size)

  | ~    ^
|  )
/export/home/defang/clamav-0.104.0-rc/libclamunrar_iface/unrar_iface.cpp:350:62: 
error: expected ')' before
  350 | unrar_dbgmsg("unrar_peek_file_header:   Unpacked Size: %" 
PRIu64 "\n", file_metadata->unpack_siz

  | ~    ^
|  )
gmake[2]: *** 
[libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/build.make:63: 
libclamunrar_iface/CMakeFilep.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1062: 
libclamunrar_iface/CMakeFiles/unrar_iface_obj.dir/all] Error 2

gmake: *** [Makefile:163: all] Error 2

Thanks

--

**
 At home during the crisis trying to work 
**
   Support Request to s...@dcs.bbk.ac.uk
**
Andrew Watkins * Birkbeck, University of London * Computer Science *
* http://notallmicrosoft.blogspot.com *
::e-mails are only read & actioned between 0900 and 1730 hours (Monday - Friday)


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Hi Henrik,

Thanks for confirming that you can make it work. I've had very poor luck 
finding the required Solaris packages to include the packages from OpenCSW.

Would you be willing to share instructions for how you install the required 
dependencies on Solaris 11.4?  It may help other Solaris users.  And while 
neither I nor my teammates are willing to do the work to continue testing on 
Solaris internally, I'd be happy to add your instructions to the online docs at 
docs.clamav.net, particularly if you're up for submitting a PR to include them 
here: 
https://github.com/Cisco-Talos/clamav-documentation/blob/main/src/manual/Installing/Installing-from-source-Unix.md

Regards,
Micah


Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.

From: clamav-users  on behalf of Henrik 
K 
Sent: Thursday, August 5, 2021 6:33 AM
To: clamav-users@lists.clamav.net 
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
here!

On Thu, Aug 05, 2021 at 12:53:57PM +0300, Henrik K wrote:
>
> Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) and
> All requirements except libcheck are OS provided, just pkg install them.

Never mind, did a bad search before, libcheck IS provided (pkg install
test/check). All tests pass:

Start 1: libclamav
1/5 Test #1: libclamav    Passed   21.18 sec
Start 2: clamscan
2/5 Test #2: clamscan .   Passed5.68 sec
Start 3: clamd
3/5 Test #3: clamd    Passed   22.56 sec
Start 4: freshclam
4/5 Test #4: freshclam    Passed2.75 sec
Start 5: sigtool
5/5 Test #5: sigtool ..   Passed0.79 sec

100% tests passed, 0 tests failed out of 5


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Henrik K]

On Thu, Aug 05, 2021 at 12:53:57PM +0300, Henrik K wrote:
>
> Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) and
> All requirements except libcheck are OS provided, just pkg install them.

Never mind, did a bad search before, libcheck IS provided (pkg install
test/check). All tests pass:

Start 1: libclamav
1/5 Test #1: libclamav    Passed   21.18 sec
Start 2: clamscan
2/5 Test #2: clamscan .   Passed5.68 sec
Start 3: clamd
3/5 Test #3: clamd    Passed   22.56 sec
Start 4: freshclam
4/5 Test #4: freshclam    Passed2.75 sec
Start 5: sigtool
5/5 Test #5: sigtool ..   Passed0.79 sec

100% tests passed, 0 tests failed out of 5


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Henrik K]

On Sat, Jul 24, 2021 at 08:17:19PM +, Micah Snyder (micasnyd) via 
clamav-users wrote:
> 
> Sorry no we don't test on Solaris anymore.  To be frank, it seems pretty
> clear that Oracle isn't maintaining Solaris anymore.  All of the packages
> are years out of date, even the opencsw ones.  It simply wasn't worth the
> effort to maintain the solaris 10 and 11 vms we used to test with.  Our
> list of systems that we test on is
> https://docs.clamav.net/#supported-platforms


No problems on Solaris 11.4.32.0.1.88.3 (SPARC) here with latest fixes,
0.104 actually works stable and fast so far.  Some more ancient versions
just kept crashing and were sloow (then again older Solaris versions had
ancient gcc etc).

Oracle DOES maintain Solaris, current 11.4 has quite recent GCC (10.2) and
other libraries (curl 7.71 etc).  All requirements except libcheck are OS
provided, just pkg install them.

Only thing that needed some manual fixing was some curses paths.

mkdir build
cd build
cmake .. \
  -D CMAKE_BUILD_TYPE="Release" \
  -D ENABLE_TESTS=OFF \
  -D PCRE2_INCLUDE_DIR=/usr/include/pcre \
  -D NCURSES_INCLUDE_DIR=/usr/include/ncurses \
  -D CURSES_LIBRARY=/usr/lib/64/libncurses.so

# Seems NCURSES_INCLUDE_DIR isn't used here..
sed -i 's###' clamav-config.h



-- Configuration Options Summary --
Package Version:ClamAV 0.104.0-rc
libclamav version:  10:0:1
libfreshclam version:   2:2:0
Install prefix: /usr/local
Install database dir:   /usr/local/share/clamav
Install config dir: /usr/local/etc
Host system:SunOS-5.11
Target system:  SunOS-5.11
Compiler:
Build type: Release
C compiler: /usr/bin/gcc
C++ compiler:   /usr/bin/c++
CFLAGS: -O3
CXXFLAGS:   -O3
WARNCFLAGS:  -Wall -Wextra -Wformat-security
Build Options:
Build apps: ON
Shared library: ON
Static library: OFF
Enable UnRAR:   ON
Examples:   OFF
Tests:  OFF
Build man pages:ON
Build doxygen HTML: OFF
Build Extras:
Build milter:   ON  (toggle with -DENABLE_MILTER=ON/OFF)
-- Engine Options --
Bytecode Runtime:
interpreter
-- libclamav Dependencies --
Compression support:
bzip2   /usr/include
/usr/lib/64/libbz2.so
zlib/usr/include
/usr/lib/64/libz.so
XML support:
libxml2 /usr/include/libxml2;/usr/include/libxml2
/usr/lib/64/libxml2.so
RegEx support:
libpcre2/usr/include/pcre
/usr/lib/64/libpcre2-8.so
Crypto support:
openssl /usr/include
/usr/lib/64/libssl.so;/usr/lib/64/libcrypto.so
JSON support:
json-c  /usr/include/json-c
/usr/lib/64/libjson-c.so
Threading support:
pthread
Locale support:
iconv   /usr/include
/usr/lib/64/libc.so
-- libfreshclam Extra Dependencies --
HTTP support:
curl/usr/include
/usr/lib/64/libcurl.so
-- Application Extra Dependencies --
GUI support:
ncurses /usr/include/ncurses
/usr/lib/64/libncurses.so
Milter Support:
libmilter   /usr/include
/usr/lib/64/libmilter.so




___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Allan via clamav-users]

Hi Micah,

Apologies for the nerd-swiping!

I'm currently setting up a VM so I can install Mussels and CMake without 
messing up my current build environment - thanks for the commands.

In terms of the install location (--prefix in autotools parlance), I'd be 
inclined to go for '/usr/local' as that tends to be where 3rd party CLI tools 
live. I think '/opt' is just where MacPorts puts stuff, and most people won't 
have that directory. '/usr/local' is supplied in a standard macOS installation, 
and is deliberately hidden from the Finder to avoid being messed with by idle 
hands!

I'll get back to you once I've got the VM set up.

Mark
PS. Would you rather take this off-list?

> On 27 Jul 2021, at 11:25 pm, Micah Snyder (micasnyd)  
> wrote:
>  
> Mark:
>  
> I’m sorry about breaking your scripts. For what it’s worth, all of the 
> dependency builds should stay the same but you’ll have to change the commands 
> for building ClamAV itself.
>  
> One of those reasons why CMake is awesome is that it’s really easy to build 
> installers. Just last week Hanspeter and I figured out how to link ClamAV 
> with a static libcurl build and have it bring along all of libcurl’s 
> dependencies. This was a roadblock for a couple things to include building a 
> PKG installer for macOS. After seeing your comments about Homebrew, and with 
> that roadblock finally removed, you successfully nerd-sniped me into figuring 
> out the rest of the macOS installer build.
>  
> I just finished a pull-request to add support to build a PKG installer for 
> Mac. I would love your input on it: 
> https://github.com/Cisco-Talos/clamav/pull/228 
> <https://github.com/Cisco-Talos/clamav/pull/228>
> Note that I picked an install path /opt/clamav rather arbitrarily.  If we’re 
> going to add a macOS PKG installer to our Downloads page, I’d appreciate 
> input on where you think it should actually install to.
>  
> My example in the PR (and commit message) rely on having used Mussels, our 
> dependency build automation tool, to build all of the static libs 
> (https://github.com/Cisco-Talos/Mussels 
> <https://github.com/Cisco-Talos/Mussels>).
> We use Mussels to build the dependencies for Windows and for Linux (for 
> OSS-Fuzz). Crafting recipes for static libs for macOS wasn’t so bad. I added 
> those last night. You can review the recipes the “clamav cookbook” uses to 
> build each dependency here: 
> https://github.com/Cisco-Talos/clamav-mussels-cookbook/ 
> <https://github.com/Cisco-Talos/clamav-mussels-cookbook/>
>  
> If you want to give it a try instead of using your own build tools, the 
> Mussels project page has some basic instructions but for a leg up here are 
> some commands to get you started:
>  
> python3 -m pip install mussels
> msl --help
> msl up
> msl cookbook trust clamav
> msl build --help
> msl build clamav_deps -t host-static --dry-run
> msl build clamav_deps -t host-static 
>  
> I have not yet modified the clamav recipe to build the PKG installer, since 
> the above PR hasn’t merged yet, but “msl build clamav -t host-static” should 
> also work.
>  
> Anyways, please let me know what you think.  
>  
> Respectfully,
> Micah
>  
>  
> From: clamav-users  <mailto:clamav-users-boun...@lists.clamav.net>> On Behalf Of Mark Allan via 
> clamav-users
> Sent: Monday, July 26, 2021 5:27 PM
> To: ClamAV users ML  <mailto:clamav-users@lists.clamav.net>>
> Cc: Mark Allan mailto:markjal...@gmail.com>>
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
> here!
>  
> I find myself asking the same question. Just from a personal point of view, 
> I've invested a lot of time over the years creating scripts that pull down 
> dependencies, build & install them in the right order, and then build package 
> and deploy ClamAV. Looks like I'll now have to spend even more time, trying 
> to get my head around making them work with CMakeand for what? What 
> benefit does it bring?
>  
> Of course, I understand that this is your project and you can do whatever you 
> like with it, and that you don't owe us any explanation for doing anything, 
> but it still seems odd to change the whole build process without at least 
> saying what the benefits are.
>  
> ...and don't get me started on the official recommendation to use Homebrew on 
> macOS.
>  
> Regards
> Mark
> 
> 
> On 26 Jul 2021, at 4:35 pm, Rick Cooper  <mailto:rcoo...@dwford.com>> wrote:
>  
> And what, exactly, is the reason for moving to cmake? I am sure you know it's 
> going to be problematic for thousands of people so I am curious what 
> tremendous gain of speed, size, memory usage or seciurity the other users get 
>

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Paul Kosinski via clamav-users]

On Wed, 28 Jul 2021 09:59:14 +0200
Matus UHLAR - fantomas  wrote:

> a bit OT, but I upgrade debian servers for years in a short steps, combining
> 
> "apt-get upgrade" so only safe packages are upgraded
> and manual upgrades a few at once via aptitude
> (so packages with complicated dependencies at the end, e.g. perl)
> 
> with configuration differences (updatedb; locate -e .dpkg- .ucf-) handled
> between those steps.
> 
> it takes a bit more time, but reduces outages.
> 
> Ubuntu can be handled similarly (however, even base ubuntu is uselessly
> bloated and has bit more complicated dependencies).



The question is, would you be willing to use the method you outlined if one bad 
package upgrade could kill your Internet access?

(Until you restored from a backup, at least.)

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi All,

I have found a bug that will cause issues for 32bit builds and maybe 
some 64bit builds.


On all three of my OS (2 x x86_64 and one x86) tested, CMake is not 
setting DEFINE_SF64_PREFIX used in clamav-types.h.in.
This breaks the build on one x86_64 OS and may cause issues on the x86 
OS with 64bit numbers.


Any ideas on how to implement a quick fix ?

Regards
Mark.

On 28/07/21 01:14, Mark Fortescue wrote:

Hi again,

I needed to read all of the INSTALL.md file not just the top bit.

Got the cmake build to work and the binaries test OK.

Not as user friendly as configure scripts when you are doing something
different. The big advantage of the configure script is that it can be
tweaked when it gets something wrong or at least opened in an editor to
see what it is actually doing. Not sure where to start if cmake does not
do what it is meant to do.

Regards
 Mark.

On 28/07/2021 00:14, Mark Fortescue via clamav-users wrote:

Hi all,

I have two curl installations. One is not suitable for clamav (the
system installed version).

How do I force cmake to pick up the correct library as it is always
picking up the system library not the one in /usr/local/clamav/lib.

In order to move to cmake it would be useful to have a conversion from
all the configure script options to there cmake equivalents. Is there
a way of getting cmake to display all the variables that can be set
(equivalent to ./configure --help) ?

Regards
 Mark.

On 22/07/2021 17:18, Joel Esler (jesler) via clamav-users wrote:




https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html



  ClamAV 0.104.0 Release Candidate is here!

We are pleased to announce the ClamAV 0.104.0 release candidate
.

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
, or on our
Discord , which is bridged with our IRC.

This release candidate phase is only expected to last about two to
four weeks before the 0.104.0 Stable version will be published. Take
this opportunity to verify that you 0.104.0 can build and run in
your environment.

Please submit bug reports to the ClamAV project GitHub Issues
.

ClamAV 0.104.0 includes the following improvements and changes.






  New Requirements

 *

As of ClamAV 0.104, CMake is required to build ClamAV.

  * We have added comprehensive build instructions for using CMake to
the new |INSTALL.md| file. The online documentation will also be
updated to include CMake build instructions.
  * The Autotools and the Visual Studio build systems have been
removed.






  Major changes

 *

The built-in LLVM for the bytecode runtime has been removed.

  * The bytecode interpreter is the default runtime for bytecode
signatures just as it was in ClamAV 0.103.
  * We wished to add support for newer versions of LLVM, but ran out
of time. If you're building ClamAV from source and you wish to use
LLVM instead of the bytecode interpreter, you will need to supply
the development libraries for LLVM version 3.6.2. See |INSTALL.md|
to learn more.
 *

There are now official ClamAV images on Docker Hub.

  o /Note/: Until ClamAV 0.104.0 is released, these images are
limited to "unstable" versions, which are updated daily with
the latest changes in the default branch on GitHub.

You can find the images on Docker Hub under |clamav|
.

Docker Hub ClamAV tags:

 *

|clamav/clamav:|: A release preloaded with signature
databases.

Using this container will save the ClamAV project some bandwidth.
Use this if you will keep the image around so that you don't
download the entire database set every time you start a new
container. Updating with FreshClam from the existing databases set
does not use much data.

 *

|clamav/clamav:_base|: A release with no signature
databases.

Use this container *only* if you mount a volume in your container
under |/var/lib/clamav| to persist your signature database
databases. This method is the best option because it will reduce
data costs for ClamAV and for the Docker registry, but it does
require advanced familiarity with Linux and Docker.

/Caution/: Using this image without mounting an existing
database directory will cause FreshClam to download the entire
database set each time you start a new container.

You can use the |unstable| version (i.e. |clamav/clamav:unstable| or
|clamav/clamav:unstable_base|) to try the latest from our
development branch.

Please, be kind when using "free" bandwidth for the virus 

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Joel Esler (jesler) via clamav-users]

> On Jul 28, 2021, at 7:17 AM, Rick Cooper  wrote:
> 
> total disregard for the user base, not so much as a poll or query on the 
> lists, enjoy your new cutting edge toys
>  
> Corporate BS rears it's ugly head again, First snort, then centos and now 
> clamav.

I think this is unfair.  This is the feedback we’re getting.  Sounds like we 
don’t need a poll or a query.  We’re hearing it now.

I also think it’s unfair to think “big bad Cisco” had anything to do with this 
at all.  ClamAV is beholden to Cisco in very few ways. In that it’s integrated 
into a few products, other than that, the ClamAV development team has pretty 
full autonomy.  No one is coming down to Micah and saying "YOU MUST YOU CMAKE 
YOU PEON DEVELOPER MUHAHAHAHAHA”.  

If you have feedback, this is the perfect use of this list to do so, but we’re 
also all adults, with jobs, with passions, and we can be professional.

As far as Snort, I think the same logic applies.  The rewrite of Snort started 
long before Cisco even entered the picture, it started when we were still 
Sourcefire back in 2011-2012.  I have the engineering slides!

smime.p7s
Description: S/MIME cryptographic signature

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Joel Esler (jesler) via clamav-users]

We are planning on making LTS versions for distros again.  

— 
Sent from my  iPad

> On Jul 28, 2021, at 07:45, Andrew C Aitchison via clamav-users 
>  wrote:
> 
> On Wed, 28 Jul 2021, Rick Cooper wrote:
> 
>> total disregard for the user base, not so much as a poll or query on the 
>> lists,
> 
> When ClamAV 0.103 was released in September 2020 CMake was an *experimental* 
> option.
> There will be a 0.103 release in September 2021, but is likely to be the last 
> one.
> 0.104 will only have CMake, no autoconfig.
> That doesn't leave much time for distributions to switch.
> 
> The latest "Long Term" Ubuntu was 2004, released about April 2020,
> the  next will be 2204, due around April 2022,
> so ClamAV will completely switch-over between sucessive Ubuntu LTS releases.
> 
> Between those LTS releases there are 3 standard/fast-track releases,
> Ubuntu2010, Oct 2020, replaced by Ubuntu2104 in April 2021 (with ClamAV 
> 0.103.2) and 2110 due in October.
> I don't see anyone from Ubuntu, Canonical or Debian here talking about
> keeping up with bleeding edge ClamAV.
> 
> Between requiring an uptodate CMake and an obsolete, 6 year old,
> LLVM, I worry that the ClamAV team is spread too thin.
> 
> -- 
> Andrew C. AitchisonKendal, UK
>and...@aitchison.me.uk
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml


smime.p7s
Description: S/MIME cryptographic signature

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Andrew C Aitchison via clamav-users]

On Wed, 28 Jul 2021, Rick Cooper wrote:


total disregard for the user base, not so much as a poll or query on the lists,


When ClamAV 0.103 was released in September 2020 CMake was an *experimental* 
option.
There will be a 0.103 release in September 2021, but is likely to be the last 
one.
0.104 will only have CMake, no autoconfig.
That doesn't leave much time for distributions to switch.

The latest "Long Term" Ubuntu was 2004, released about April 2020,
the  next will be 2204, due around April 2022,
so ClamAV will completely switch-over between sucessive Ubuntu LTS 
releases.


Between those LTS releases there are 3 standard/fast-track releases,
Ubuntu2010, Oct 2020, replaced by Ubuntu2104 in April 2021 (with ClamAV 
0.103.2) and 2110 due in October.

I don't see anyone from Ubuntu, Canonical or Debian here talking about
keeping up with bleeding edge ClamAV.

Between requiring an uptodate CMake and an obsolete, 6 year old,
LLVM, I worry that the ClamAV team is spread too thin.

--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Rick Cooper]

Ok that was the answer. It was done because the development team wanted new
toys and the fact that you have to include instructions as to how to go
about building cmake (and using a version that requires a fairly new
distro). And cmake is constantly releasing new updates which, in my mind,
puts it right up there with Fedora in terms of "ready for production".
Autotools was at least a staple that pretty much and pretty much any end
user could run the configure command and end up with a functional program
without having to install a whole new build.
system.
 
total disregard for the user base, not so much as a poll or query on the
lists, enjoy your new cutting edge toys
 
Corporate BS rears it's ugly head again, First snort, then centos and now
clamav.
 
 

  _  

From: clamav-users [mailto:clamav-users-boun...@lists.clamav.net] On Behalf
Of Micah Snyder (micasnyd) via clamav-users
Sent: Tuesday, July 27, 2021 6:26 PM
To: ClamAV users ML
Cc: Micah Snyder (micasnyd)
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
is here!



All:

 

I and others on the development team struggled with Autotools and felt
plagued by a myriad of little bugs. Whenever we had a problem with autotools
(and there were plenty) it was always, “Heeey you’re the Autotools expert.
You got this, right?…” No one wanted to deal with it. 

 

CMake is far less confusing and less error-prone (at least to me). The
documentation is great. It has built in features to detect loads of
system-installed libraries. More recent versions even have system similar to
pkg-config for importing build targets exactly as they were created when
compiled, so that you never miss a library dependency. No more mussing about
with LDFLAGS and LIBS variables and various directory variables. Honestly,
it’s a breath of fresh air. And CMake supports Windows which allowed us to
drop the old Visual Studio project files. There’s more, but I think that
should be enough. No it won’t necessarily improve detection, unless you were
one of those people who didn’t realize you needed libbz2 or some such
“optional” dependency in order to get the most out of ClamAV. 

 

Anyways, there are many reasons why CMake is better than Autotools but I
don’t want to ramble on about it any more than I already have. I recommend
reading up on some modern CMake features. You may find that you like it. 

 

But if you really don’t want to deal with it, you can wait until your
system’s packaging system has the next ClamAV version. That’s what most
people will do anyways.

 

Mark:

 

I’m sorry about breaking your scripts. For what it’s worth, all of the
dependency builds should stay the same but you’ll have to change the
commands for building ClamAV itself.

 

One of those reasons why CMake is awesome is that it’s really easy to build
installers. Just last week Hanspeter and I figured out how to link ClamAV
with a static libcurl build and have it bring along all of libcurl’s
dependencies. This was a roadblock for a couple things to include building a
PKG installer for macOS. After seeing your comments about Homebrew, and with
that roadblock finally removed, you successfully nerd-sniped me into
figuring out the rest of the macOS installer build.

 

I just finished a pull-request to add support to build a PKG installer for
Mac. I would love your input on it:
https://github.com/Cisco-Talos/clamav/pull/228

Note that I picked an install path /opt/clamav rather arbitrarily.  If we’re
going to add a macOS PKG installer to our Downloads page, I’d appreciate
input on where you think it should actually install to.

 

My example in the PR (and commit message) rely on having used Mussels, our
dependency build automation tool, to build all of the static libs
(https://github.com/Cisco-Talos/Mussels). 

We use Mussels to build the dependencies for Windows and for Linux (for
OSS-Fuzz). Crafting recipes for static libs for macOS wasn’t so bad. I added
those last night. You can review the recipes the “clamav cookbook” uses to
build each dependency here:
https://github.com/Cisco-Talos/clamav-mussels-cookbook/

 

If you want to give it a try instead of using your own build tools, the
Mussels project page has some basic instructions but for a leg up here are
some commands to get you started:

 

python3 -m pip install mussels

msl --help

msl up

msl cookbook trust clamav

msl build --help

msl build clamav_deps -t host-static --dry-run

msl build clamav_deps -t host-static 

 

I have not yet modified the clamav recipe to build the PKG installer, since
the above PR hasn’t merged yet, but “msl build clamav -t host-static” should
also work. 

 

Anyways, please let me know what you think.  

 

Respectfully,

Micah

 

 

From: clamav-users  On Behalf Of Mark
Allan via clamav-users
Sent: Monday, July 26, 2021 5:27 PM
To: ClamAV users ML 
Cc: Mark Allan 
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
is here!

 

I find myself asking the sam

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Matus UHLAR - fantomas]

On Tue, 27 Jul 2021 16:41:03 +0100
Mark Fortescue via clamav-users  wrote:

One quick answer to why people do not upgrade the OS is that the
hardware does not support the upgrade (mostly due to memory and x86_64).

I work with embedded systems where the code is very specific to the
hardware so new hardware is not an option.

For others it may just be the hassle of starting setting up a new OS and
fixing all the distribution bugs/annoyances that get installed with each
new OS all over again.


On 28.07.21 00:26, Paul Kosinski via clamav-users wrote:

In my case, I can't simply upgrade to the latest Debian (or any other
distro), as one of the systems is our home firewall and gateway -- with
iptables, multi-LAN routing (with local DNS), a bit of bridging, encrypted
tunnels to elsewhere, etc.  This means we would lose *all* Internet
connectivity for who knows how long if I tried an in-place upgrade.


a bit OT, but I upgrade debian servers for years in a short steps, combining

"apt-get upgrade" so only safe packages are upgraded
and manual upgrades a few at once via aptitude
(so packages with complicated dependencies at the end, e.g. perl)

with configuration differences (updatedb; locate -e .dpkg- .ucf-) handled
between those steps.

it takes a bit more time, but reduces outages.

Ubuntu can be handled similarly (however, even base ubuntu is uselessly
bloated and has bit more complicated dependencies).

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Paul Kosinski via clamav-users]

On Tue, 27 Jul 2021 16:41:03 +0100
Mark Fortescue via clamav-users  wrote:

> Hi Joel,
> 
> One quick answer to why people do not upgrade the OS is that the 
> hardware does not support the upgrade (mostly due to memory and x86_64).
> 
> I work with embedded systems where the code is very specific to the 
> hardware so new hardware is not an option.
> 
> For others it may just be the hassle of starting setting up a new OS and 
> fixing all the distribution bugs/annoyances that get installed with each 
> new OS all over again.
> 
> Regards
>   Mark.


In my case, I can't simply upgrade to the latest Debian (or any other distro), 
as one of the systems is our home firewall and gateway -- with iptables, 
multi-LAN routing (with local DNS), a bit of bridging, encrypted tunnels to 
elsewhere, etc. This means we would lose *all* Internet connectivity for who 
knows how long if I tried an in-place upgrade.

So the only way to move forward seems to be to rebuild our system on separate 
hardware. I have started this on hardware I already mainly have (being retired, 
and thus without corporate budget or staff). Then I plan get the new build more 
or less working, and hope that I don't have to move cables between the old and 
new (and change IP addresses back and forth) more than a few times, thereby 
only having a few short periods of time without Internet connectivity.

Finally, building this new system is made even more difficult by the fact that 
iptables has recently been replaced by nftables, whose native syntax has been 
"improved" to be quite different. There is, at least, a legacy iptables 
interface to it, and it may actually be behaviorally identical to the old 
iptables for my > 2000 custom rules (built up over a dozen years) which govern 
LAN[i] <=> LAN[j] and LAN[i] <=> Internet routing and firewalling.

P.S. The last time I upgraded our firewall, from x86 to x86_64, at least 
iptables was quite compatible with ipchains, and Linux as a whole was still in 
the early stages of its exponential growth in complexity.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi again,

I needed to read all of the INSTALL.md file not just the top bit.

Got the cmake build to work and the binaries test OK.

Not as user friendly as configure scripts when you are doing something 
different. The big advantage of the configure script is that it can be 
tweaked when it gets something wrong or at least opened in an editor to 
see what it is actually doing. Not sure where to start if cmake does not 
do what it is meant to do.


Regards
Mark.

On 28/07/2021 00:14, Mark Fortescue via clamav-users wrote:

Hi all,

I have two curl installations. One is not suitable for clamav (the 
system installed version).


How do I force cmake to pick up the correct library as it is always 
picking up the system library not the one in /usr/local/clamav/lib.


In order to move to cmake it would be useful to have a conversion from 
all the configure script options to there cmake equivalents. Is there a 
way of getting cmake to display all the variables that can be set 
(equivalent to ./configure --help) ?


Regards
 Mark.

On 22/07/2021 17:18, Joel Esler (jesler) via clamav-users wrote:




https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html 




  ClamAV 0.104.0 Release Candidate is here!

We are pleased to announce the ClamAV 0.104.0 release candidate 
.


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 
, or on our 
Discord , which is bridged with our IRC.


This release candidate phase is only expected to last about two to 
four weeks before the 0.104.0 Stable version will be published. Take 
this opportunity to verify that you 0.104.0 can build and run in your 
environment.


Please submit bug reports to the ClamAV project GitHub Issues 
.


ClamAV 0.104.0 includes the following improvements and changes.


  
 




  New Requirements

 *

    As of ClamAV 0.104, CMake is required to build ClamAV.

  * We have added comprehensive build instructions for using CMake to
    the new |INSTALL.md| file. The online documentation will also be
    updated to include CMake build instructions.
  * The Autotools and the Visual Studio build systems have been removed.


  
 




  Major changes

 *

    The built-in LLVM for the bytecode runtime has been removed.

  * The bytecode interpreter is the default runtime for bytecode
    signatures just as it was in ClamAV 0.103.
  * We wished to add support for newer versions of LLVM, but ran out
    of time. If you're building ClamAV from source and you wish to use
    LLVM instead of the bytecode interpreter, you will need to supply
    the development libraries for LLVM version 3.6.2. See |INSTALL.md|
    to learn more.
 *

    There are now official ClamAV images on Docker Hub.

  o /Note/: Until ClamAV 0.104.0 is released, these images are
    limited to "unstable" versions, which are updated daily with
    the latest changes in the default branch on GitHub.

You can find the images on Docker Hub under |clamav| 
.


Docker Hub ClamAV tags:

 *

    |clamav/clamav:|: A release preloaded with signature
    databases.

    Using this container will save the ClamAV project some bandwidth.
    Use this if you will keep the image around so that you don't
    download the entire database set every time you start a new
    container. Updating with FreshClam from the existing databases set
    does not use much data.

 *

    |clamav/clamav:_base|: A release with no signature 
databases.


    Use this container *only* if you mount a volume in your container
    under |/var/lib/clamav| to persist your signature database
    databases. This method is the best option because it will reduce
    data costs for ClamAV and for the Docker registry, but it does
    require advanced familiarity with Linux and Docker.

    /Caution/: Using this image without mounting an existing
    database directory will cause FreshClam to download the entire
    database set each time you start a new container.

You can use the |unstable| version (i.e. |clamav/clamav:unstable| or 
|clamav/clamav:unstable_base|) to try the latest from our development 
branch.


Please, be kind when using "free" bandwidth for the virus databases 
and Docker registry. Try not to download the entire database set or 
the larger ClamAV database images on a regular basis.


For more details, see the ClamAV Docker documentation 
.


Special thanks to Olliver Schinagl for his excellent work creating 
ClamAV's new Docker files, image database deployment 

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi all,

I have two curl installations. One is not suitable for clamav (the 
system installed version).


How do I force cmake to pick up the correct library as it is always 
picking up the system library not the one in /usr/local/clamav/lib.


In order to move to cmake it would be useful to have a conversion from 
all the configure script options to there cmake equivalents. Is there a 
way of getting cmake to display all the variables that can be set 
(equivalent to ./configure --help) ?


Regards
Mark.

On 22/07/2021 17:18, Joel Esler (jesler) via clamav-users wrote:




https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html


  ClamAV 0.104.0 Release Candidate is here!

We are pleased to announce the ClamAV 0.104.0 release candidate 
.


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 
, or on our 
Discord , which is bridged with our IRC.


This release candidate phase is only expected to last about two to 
four weeks before the 0.104.0 Stable version will be published. Take 
this opportunity to verify that you 0.104.0 can build and run in your 
environment.


Please submit bug reports to the ClamAV project GitHub Issues 
.


ClamAV 0.104.0 includes the following improvements and changes.


  



  New Requirements

 *

As of ClamAV 0.104, CMake is required to build ClamAV.

  * We have added comprehensive build instructions for using CMake to
the new |INSTALL.md| file. The online documentation will also be
updated to include CMake build instructions.
  * The Autotools and the Visual Studio build systems have been removed.


  



  Major changes

 *

The built-in LLVM for the bytecode runtime has been removed.

  * The bytecode interpreter is the default runtime for bytecode
signatures just as it was in ClamAV 0.103.
  * We wished to add support for newer versions of LLVM, but ran out
of time. If you're building ClamAV from source and you wish to use
LLVM instead of the bytecode interpreter, you will need to supply
the development libraries for LLVM version 3.6.2. See |INSTALL.md|
to learn more.
 *

There are now official ClamAV images on Docker Hub.

  o /Note/: Until ClamAV 0.104.0 is released, these images are
limited to "unstable" versions, which are updated daily with
the latest changes in the default branch on GitHub.

You can find the images on Docker Hub under |clamav| 
.


Docker Hub ClamAV tags:

 *

|clamav/clamav:|: A release preloaded with signature
databases.

Using this container will save the ClamAV project some bandwidth.
Use this if you will keep the image around so that you don't
download the entire database set every time you start a new
container. Updating with FreshClam from the existing databases set
does not use much data.

 *

|clamav/clamav:_base|: A release with no signature databases.

Use this container *only* if you mount a volume in your container
under |/var/lib/clamav| to persist your signature database
databases. This method is the best option because it will reduce
data costs for ClamAV and for the Docker registry, but it does
require advanced familiarity with Linux and Docker.

/Caution/: Using this image without mounting an existing
database directory will cause FreshClam to download the entire
database set each time you start a new container.

You can use the |unstable| version (i.e. |clamav/clamav:unstable| or 
|clamav/clamav:unstable_base|) to try the latest from our development 
branch.


Please, be kind when using "free" bandwidth for the virus databases 
and Docker registry. Try not to download the entire database set or 
the larger ClamAV database images on a regular basis.


For more details, see the ClamAV Docker documentation 
.


Special thanks to Olliver Schinagl for his excellent work creating 
ClamAV's new Docker files, image database deployment tooling, and user 
documentation.


 *

|clamd| and |freshclam| are now available as Windows services. To
install and run them, use the |--install-service| option and |net
start [name]| command.

Special thanks to Gianluigi Tiesi for his original work on this
feature.


  



  Notable changes

We added these features in 0.103.1 but wanted to re-post them here, as 
patch versions do not generally introduce new options:


 *

Added a new 

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

All:

I and others on the development team struggled with Autotools and felt plagued 
by a myriad of little bugs. Whenever we had a problem with autotools (and there 
were plenty) it was always, “Heeey you’re the Autotools expert. You got this, 
right?…” No one wanted to deal with it.

CMake is far less confusing and less error-prone (at least to me). The 
documentation is great. It has built in features to detect loads of 
system-installed libraries. More recent versions even have system similar to 
pkg-config for importing build targets exactly as they were created when 
compiled, so that you never miss a library dependency. No more mussing about 
with LDFLAGS and LIBS variables and various directory variables. Honestly, it’s 
a breath of fresh air. And CMake supports Windows which allowed us to drop the 
old Visual Studio project files. There’s more, but I think that should be 
enough. No it won’t necessarily improve detection, unless you were one of those 
people who didn’t realize you needed libbz2 or some such “optional” dependency 
in order to get the most out of ClamAV.

Anyways, there are many reasons why CMake is better than Autotools but I don’t 
want to ramble on about it any more than I already have. I recommend reading up 
on some modern CMake features. You may find that you like it.

But if you really don’t want to deal with it, you can wait until your system’s 
packaging system has the next ClamAV version. That’s what most people will do 
anyways.

Mark:

I’m sorry about breaking your scripts. For what it’s worth, all of the 
dependency builds should stay the same but you’ll have to change the commands 
for building ClamAV itself.

One of those reasons why CMake is awesome is that it’s really easy to build 
installers. Just last week Hanspeter and I figured out how to link ClamAV with 
a static libcurl build and have it bring along all of libcurl’s dependencies. 
This was a roadblock for a couple things to include building a PKG installer 
for macOS. After seeing your comments about Homebrew, and with that roadblock 
finally removed, you successfully nerd-sniped me into figuring out the rest of 
the macOS installer build.

I just finished a pull-request to add support to build a PKG installer for Mac. 
I would love your input on it: https://github.com/Cisco-Talos/clamav/pull/228
Note that I picked an install path /opt/clamav rather arbitrarily.  If we’re 
going to add a macOS PKG installer to our Downloads page, I’d appreciate input 
on where you think it should actually install to.

My example in the PR (and commit message) rely on having used Mussels, our 
dependency build automation tool, to build all of the static libs 
(https://github.com/Cisco-Talos/Mussels).
We use Mussels to build the dependencies for Windows and for Linux (for 
OSS-Fuzz). Crafting recipes for static libs for macOS wasn’t so bad. I added 
those last night. You can review the recipes the “clamav cookbook” uses to 
build each dependency here: 
https://github.com/Cisco-Talos/clamav-mussels-cookbook/

If you want to give it a try instead of using your own build tools, the Mussels 
project page has some basic instructions but for a leg up here are some 
commands to get you started:

python3 -m pip install mussels
msl --help
msl up
msl cookbook trust clamav
msl build --help
msl build clamav_deps -t host-static --dry-run
msl build clamav_deps -t host-static

I have not yet modified the clamav recipe to build the PKG installer, since the 
above PR hasn’t merged yet, but “msl build clamav -t host-static” should also 
work.

Anyways, please let me know what you think.

Respectfully,
Micah


From: clamav-users  On Behalf Of Mark 
Allan via clamav-users
Sent: Monday, July 26, 2021 5:27 PM
To: ClamAV users ML 
Cc: Mark Allan 
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
here!

I find myself asking the same question. Just from a personal point of view, 
I've invested a lot of time over the years creating scripts that pull down 
dependencies, build & install them in the right order, and then build package 
and deploy ClamAV. Looks like I'll now have to spend even more time, trying to 
get my head around making them work with CMakeand for what? What benefit 
does it bring?

Of course, I understand that this is your project and you can do whatever you 
like with it, and that you don't owe us any explanation for doing anything, but 
it still seems odd to change the whole build process without at least saying 
what the benefits are.

...and don't get me started on the official recommendation to use Homebrew on 
macOS.

Regards
Mark


On 26 Jul 2021, at 4:35 pm, Rick Cooper 
mailto:rcoo...@dwford.com>> wrote:

And what, exactly, is the reason for moving to cmake? I am sure you know it's 
going to be problematic for thousands of people so I am curious what tremendous 
gain of speed, size, memory usage or seciurity the other users get from this 
change, or if it's just a conveni

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Paul Kosinski via clamav-users]

On Tue, 27 Jul 2021 15:30:05 +
"Joel Esler (jesler)"  wrote:

> You can’t support everything, forever.

When you are part of critical infrastructure -- as computers have become -- you 
must. (Well, not quite forever.)

Compare the rollout of IPv6 with the rollout of x86_64 (not to mention the 
rollout years ago of Area Codes and Direct Distance Dialing).

IPv6 is better than IPv4 in providing many more IP addresses, but it hasn't 
replaced it: it's incompatible. (Why didn't they simply add more bits, like 
int32 => int64?)

In CPUs, x86_64, which is backward compatible, has taken over, while its 
"replacement", Itanium is gone. (ARM is spreading, of course, but not because 
x86_64 is being dropped upon software upgrade; even Apple can't do that for a 
few years).

And imagine what would have happened 50 years ago if you had needed new 
telephones and a second telephone number to take advantage of DDD.

Of course ClamAV now belongs to Cisco, and there is no money cost to users, but 
the work cost to keep up-to-date has gotten much worse recently (mainly because 
of the response to bandwidth abuse), and some less dedicated users are probably 
giving up.


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Tue, 27 Jul 2021, Joel Esler wrote:

On Jul 27, 2021, at 11:27 AM, Paul Kosinski wrote:

On Mon, 26 Jul 2021 11:35:29 Rick Cooper wrote:


And what, exactly, is the reason for moving to cmake? I am sure
you know it's going to be problematic for thousands of people so I
am curious what tremendous gain of speed, size, memory usage or
seciurity the other users get from this change, or if it's just a
convenience thing for the developers?


I get the impression that *all* recent software development (at
least in Open Source) has given up any notion of backward
compatibility. ...

Now I wonder what will happen when I next try to build ClamAV on my
three different Debian systems (7, 8 & 10).


You can’t support everything, forever.  You have to push forward
with new tools and technology that make securing your customers
easier and better and provide more functionality to us (the authors
of the ruleset) to better protect people (you).


I could get alongside this if I could see the evidence that the better
security and functionality was actually happening.  We're still stuck
with version 2 of Yara, and a parser that's so riddled that I've often
considered Python tools instead.  Despite being swallowed up by Cisco,
(a near hundred-billion-dollar corporation) eight years ago, ClamAV is
*still* very near the bottom of my detection rates league table:

https://marc.info/?l=clamav-users=162379914711853=2

If 'cmake' is going to change all that, please tell me how - and when.


If you’re using security software to protect yourself, why would you
not do the most basic things and upgrade the OS of the systems ... ?


While I'd agree in principle with the sentiment, there are some people
who are stuck with legacy software which makes upgrade very difficult.
Despite my warnings about the gear, I've seen clients make seven-digit
GBP investments in machine tools which rely on Windows XP, expecting
the tools to operate long after Winows XP reaches EOL, no upgrade path
whatever available.  There are accounting and ERP packages clinging on
by their fingernails too.  It sometimes seems like the only way to get
rid of them is to get the tax authorities to mandate some new feature
which they don't support.  There's a real world out there, and it's
unsatisfactory from many points of view, but it's the one we've got.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi Joel,

One quick answer to why people do not upgrade the OS is that the 
hardware does not support the upgrade (mostly due to memory and x86_64).


I work with embedded systems where the code is very specific to the 
hardware so new hardware is not an option.


For others it may just be the hassle of starting setting up a new OS and 
fixing all the distribution bugs/annoyances that get installed with each 
new OS all over again.


Regards
Mark.

On 27/07/2021 16:30, Joel Esler (jesler) via clamav-users wrote:



On Jul 27, 2021, at 11:27 AM, Paul Kosinski via clamav-users 
mailto:clamav-users@lists.clamav.net>> 
wrote:


On Mon, 26 Jul 2021 11:35:29 -0400
"Rick Cooper" mailto:rcoo...@dwford.com>> wrote:


And what, exactly, is the reason for moving to cmake? I am sure you know
it's going to be problematic for thousands of people so I am curious what
tremendous gain of speed, size, memory usage or seciurity the other users
get from this change, or if it's just a convenience thing for the
developers?



I get the impression that *all* recent software development (at least 
in Open Source) has given up any notion of backward compatibility. For 
example, Firefox (even ESR) has been a disaster in the past few years, 
changing the UI with every major release, once totally blowing away 
users' bookmarks, and of course, completely invalidating many, many 
years of add-on development by many people due to switching from XUL 
to the less powerful WebExtensions.


Now I wonder what will happen when I next try to build ClamAV on my 
three different Debian systems (7, 8 & 10).


You can’t support everything, forever.  You have to push forward with 
new tools and technology that make securing your customers easier and 
better and provide more functionality to us (the authors of the ruleset) 
to better protect people (you).


If you’re using security software to protect yourself, why would you not 
do the most basic things and upgrade the OS of the systems underneath? 
  I never understood this.



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Joel Esler (jesler) via clamav-users]

> On Jul 27, 2021, at 11:27 AM, Paul Kosinski via clamav-users 
>  wrote:
> 
> On Mon, 26 Jul 2021 11:35:29 -0400
> "Rick Cooper" mailto:rcoo...@dwford.com>> wrote:
> 
>> And what, exactly, is the reason for moving to cmake? I am sure you know
>> it's going to be problematic for thousands of people so I am curious what
>> tremendous gain of speed, size, memory usage or seciurity the other users
>> get from this change, or if it's just a convenience thing for the
>> developers?
> 
> 
> I get the impression that *all* recent software development (at least in Open 
> Source) has given up any notion of backward compatibility. For example, 
> Firefox (even ESR) has been a disaster in the past few years, changing the UI 
> with every major release, once totally blowing away users' bookmarks, and of 
> course, completely invalidating many, many years of add-on development by 
> many people due to switching from XUL to the less powerful WebExtensions.
> 
> Now I wonder what will happen when I next try to build ClamAV on my three 
> different Debian systems (7, 8 & 10).

You can’t support everything, forever.  You have to push forward with new tools 
and technology that make securing your customers easier and better and provide 
more functionality to us (the authors of the ruleset) to better protect people 
(you).

If you’re using security software to protect yourself, why would you not do the 
most basic things and upgrade the OS of the systems underneath?  I never 
understood this.

smime.p7s
Description: S/MIME cryptographic signature

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Paul Kosinski via clamav-users]

On Mon, 26 Jul 2021 11:35:29 -0400
"Rick Cooper"  wrote:

> And what, exactly, is the reason for moving to cmake? I am sure you know
> it's going to be problematic for thousands of people so I am curious what
> tremendous gain of speed, size, memory usage or seciurity the other users
> get from this change, or if it's just a convenience thing for the
> developers?


I get the impression that *all* recent software development (at least in Open 
Source) has given up any notion of backward compatibility. For example, Firefox 
(even ESR) has been a disaster in the past few years, changing the UI with 
every major release, once totally blowing away users' bookmarks, and of course, 
completely invalidating many, many years of add-on development by many people 
due to switching from XUL to the less powerful WebExtensions.

Now I wonder what will happen when I next try to build ClamAV on my three 
different Debian systems (7, 8 & 10).

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Allan via clamav-users]

I find myself asking the same question. Just from a personal point of view, 
I've invested a lot of time over the years creating scripts that pull down 
dependencies, build & install them in the right order, and then build package 
and deploy ClamAV. Looks like I'll now have to spend even more time, trying to 
get my head around making them work with CMakeand for what? What benefit 
does it bring?

Of course, I understand that this is your project and you can do whatever you 
like with it, and that you don't owe us any explanation for doing anything, but 
it still seems odd to change the whole build process without at least saying 
what the benefits are.

...and don't get me started on the official recommendation to use Homebrew on 
macOS.

Regards
Mark

> On 26 Jul 2021, at 4:35 pm, Rick Cooper  wrote:
> 
> And what, exactly, is the reason for moving to cmake? I am sure you know it's 
> going to be problematic for thousands of people so I am curious what 
> tremendous gain of speed, size, memory usage or seciurity the other users get 
> from this change, or if it's just a convenience thing for the developers?
>  
>  
> 
> From: clamav-users [mailto:clamav-users-boun...@lists.clamav.net] On Behalf 
> Of Joel Esler (jesler) via clamav-users
> Sent: Thursday, July 22, 2021 12:19 PM
> To: ClamAV users ML; ClamAV Development
> Cc: Joel Esler (jesler)
> Subject: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is 
> here!
> 
> 
>> 
>> https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html 
>> <https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html>
>> 
>> ClamAV 0.104.0 Release Candidate is here!
>> 
>> We are pleased to announce the ClamAV 0.104.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>, or on our Discord 
>> <https://discord.gg/sGaxA5Q>, which is bridged with our IRC.
>> 
>> This release candidate phase is only expected to last about two to four 
>> weeks before the 0.104.0 Stable version will be published. Take this 
>> opportunity to verify that you 0.104.0 can build and run in your 
>> environment. 
>> 
>>  <>Please submit bug reports to the ClamAV project GitHub Issues 
>> <https://github.com/Cisco-Talos/clamav/issues>.  
>> ClamAV 0.104.0 includes the following improvements and changes.
>> 
>>  
>> <https://github.com/Cisco-Talos/clamav/blob/dev/0.104/NEWS.md#new-requirements>
>> New Requirements
>> 
>> As of ClamAV 0.104, CMake is required to build ClamAV.
>> 
>> We have added comprehensive build instructions for using CMake to the new 
>> INSTALL.md file. The online documentation will also be updated to include 
>> CMake build instructions.
>> The Autotools and the Visual Studio build systems have been removed.
>>  <https://github.com/Cisco-Talos/clamav/blob/dev/0.104/NEWS.md#major-changes>
>> Major changes
>> 
>> The built-in LLVM for the bytecode runtime has been removed.
>> 
>> The bytecode interpreter is the default runtime for bytecode signatures just 
>> as it was in ClamAV 0.103.
>> We wished to add support for newer versions of LLVM, but ran out of time. If 
>> you're building ClamAV from source and you wish to use LLVM instead of the 
>> bytecode interpreter, you will need to supply the development libraries for 
>> LLVM version 3.6.2. See INSTALL.md to learn more.
>> There are now official ClamAV images on Docker Hub.
>> 
>> Note: Until ClamAV 0.104.0 is released, these images are limited to 
>> "unstable" versions, which are updated daily with the latest changes in the 
>> default branch on GitHub.
>> You can find the images on Docker Hub under clamav 
>> <https://hub.docker.com/r/clamav/clamav>.
>> 
>> Docker Hub ClamAV tags:
>> 
>> clamav/clamav:: A release preloaded with signature databases.
>> 
>> Using this container will save the ClamAV project some bandwidth. Use this 
>> if you will keep the image around so that you don't download the entire 
>> database set every time you start a new container. Updating with FreshClam 
>> from the existing databases set does not use much data.
>> 
>> clamav/clamav:_base: A release with no signature databases.
>> 
>> Use this container only if you mount a volume in your container under 
>> /var/lib/clamav to persist your signature database databases. This metho

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Hi Arjen,

The '-D ENABLE_UNRAR=OFF' test failure issue is definitely not expected!  I 
think that one should be an easy enough fix. 

If you're up for it, it would be helpful to add a GitHub issue for this bug: 
https://github.com/Cisco-Talos/clamav/issues
I will make a note to add a test case in our custom tests pipeline for having 
UNRAR disabled. 

The other issue with iconv if also not expected.  We haven't been testing with 
openSUSE.  I think we should also add an openSUSE docker container to our CI 
pipeline.

I gave it a try in a docker container just now on my laptop. For me it detected 
iconv as being in libc, but failed the libclamav unit tests with:

1: 99%: Checks: 1127, Failures: 4, Errors: 0
1: /clamav/unit_tests/check_clamav.c:1460:F:assorted 
functions:test_cli_codepage_to_utf8_jis:0: test_cli_codepage_to_utf8: Failed to 
convert CODEPAGE_JAPANESE_SHIFT_JIS to UTF8: ret != SUCCESS!
1: /clamav/unit_tests/check_clamav.c:1478:F:assorted 
functions:test_cli_codepage_to_utf8_utf16be_null_term:0: 
test_cli_codepage_to_utf8: Failed to convert CODEPAGE_UTF16_BE to UTF8: ret != 
SUCCESS!
1: /clamav/unit_tests/check_clamav.c:1496:F:assorted 
functions:test_cli_codepage_to_utf8_utf16be_no_null_term:0: 
test_cli_codepage_to_utf8: Failed to convert CODEPAGE_UTF16_BE to UTF8: ret != 
SUCCESS!
1: /clamav/unit_tests/check_clamav.c:1514:F:assorted 
functions:test_cli_codepage_to_utf8_utf16le:0: test_cli_codepage_to_utf8: 
Failed to convert CODEPAGE_UTF16_LE to UTF8: ret != SUCCESS!
1: NOTICE: Use the 'T' environment variable to adjust testcase timeout

We used to have similar failures for Alpine but fixed those. If you can submit 
a second issue for this one as well, I would very much appreciate it.

Regards,
Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> Arjen de Korte via clamav-users
> Sent: Sunday, July 25, 2021 11:50 AM
> To: ClamAV users ML 
> Cc: Arjen de Korte 
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> Citeren Arjen de Korte via clamav-users :
> 
> > [6s] -- Performing Test Iconv_IS_BUILT_IN
> > [6s] -- Performing Test Iconv_IS_BUILT_IN - Failed
> > [6s] CMake Error at
> > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230
> > (message):
> > [6s]   Could NOT find Iconv (missing: Iconv_LIBRARY)
> > [6s] Call Stack (most recent call first):
> > [6s]
> > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594
> > (_FPHSA_FAILURE_MESSAGE)
> > [6s]   cmake/FindIconv.cmake:129 (find_package_handle_standard_args)
> > [6s]   CMakeLists.txt:332 (find_package)
> 
> Apparently this test is not able to determine if iconv is actually built-in. 
> Adding
> '-D Iconv_IS_BUILT_IN=ON' to the cmake command line, fixes this. If this is 
> the
> intended behavior, it might be useful to change the error message (it took me 
> a
> while to figure out that iconv was actually built-in).
> 
> Another thing is that when adding '-D ENABLE_UNRAR=OFF' to the cmake
> command line, one also has to set '-D ENABLE_TESTS=OFF', otherwise the build
> will fail fairly quickly due to the following error.
> 
>  Error evaluating generator expression:
> 
>$
> 
>  No target "ClamAV::libunrar_iface"
> 
> errors. Not sure if this is expected though.
> 
> Other than this, the build seems to succeed on openSUSE Tumbleweed and the
> resulting binaries seem to run fine.
> 
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

On 7/26/21 8:55 PM, Micah Snyder (micasnyd) via clamav-users wrote:

I read Ged's response as "I would create a bugzilla ticket" not "I will create a 
bugzilla ticket". I can't speak to what he may have told you directly.
But I don't see a new ticket on this subject in bugzilla or github issues. I 
would prefer github issues but will be happy with a ticket in either system.

-Micah


-Original Message-
From: clamav-users  On Behalf Of
Frans de Boer
Sent: Monday, July 26, 2021 11:48 AM
To: clamav-users@lists.clamav.net
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
is here!

n 7/26/21 8:39 PM, Micah Snyder (micasnyd) via clamav-users wrote:

Frans,

Can you please create a ticket on https://github.com/Cisco-

Talos/clamav/issues for the clamd test failure? Please attach the verbose
output from running:

ctest -V

Regarding make -j [n] vs ninja -- yes it's not a huge difference.  It's just a

convenience if you're compiling a lot.  We should probably remove the ninja
suggestion from the INSTALL.md file.

I didn't include it in
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.
html We do mention it here, which is good enough:
https://docs.clamav.net/manual/Development/development-builds.html

-Micah


-Original Message-
From: clamav-users  On Behalf
Of Frans de Boer
Sent: Sunday, July 25, 2021 11:08 AM
To: clamav-users@lists.clamav.net
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release
Candidate is here!

I get things compiled etc., but testing clamd keeps on failing. I
tried three different machines/CPU's to no avail.

I use OpenSUSE Tumbleweed with newest cmake etc.

One remark: using 'make -j [n]' instead of ninja only takes less than
2 seconds longer to build things. So, the 'big speed up' is only a
'very minor speed up'. Of course if you compile a very large amount
of software every day, multiple times a day, those less than 2 seconds do

add up.

Any suggestion what data I can provide to find the cause of the failure?

Regards, Frans.

G.W. Haywood told me he would make a ticket. He also - just as the whole list -
has the full Testlog.log file since 25/7.

--- Frans.


Never mind, just posted it on github too, as requested.

Frans

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

I read Ged's response as "I would create a bugzilla ticket" not "I will create 
a bugzilla ticket". I can't speak to what he may have told you directly.
But I don't see a new ticket on this subject in bugzilla or github issues. I 
would prefer github issues but will be happy with a ticket in either system.

-Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> Frans de Boer
> Sent: Monday, July 26, 2021 11:48 AM
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> n 7/26/21 8:39 PM, Micah Snyder (micasnyd) via clamav-users wrote:
> > Frans,
> >
> > Can you please create a ticket on https://github.com/Cisco-
> Talos/clamav/issues for the clamd test failure? Please attach the verbose
> output from running:
> >ctest -V
> >
> > Regarding make -j [n] vs ninja -- yes it's not a huge difference.  It's 
> > just a
> convenience if you're compiling a lot.  We should probably remove the ninja
> suggestion from the INSTALL.md file.
> > I didn't include it in
> > https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.
> > html We do mention it here, which is good enough:
> > https://docs.clamav.net/manual/Development/development-builds.html
> >
> > -Micah
> >
> >> -Original Message-
> >> From: clamav-users  On Behalf
> >> Of Frans de Boer
> >> Sent: Sunday, July 25, 2021 11:08 AM
> >> To: clamav-users@lists.clamav.net
> >> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release
> >> Candidate is here!
> >>
> >> I get things compiled etc., but testing clamd keeps on failing. I
> >> tried three different machines/CPU's to no avail.
> >>
> >> I use OpenSUSE Tumbleweed with newest cmake etc.
> >>
> >> One remark: using 'make -j [n]' instead of ninja only takes less than
> >> 2 seconds longer to build things. So, the 'big speed up' is only a
> >> 'very minor speed up'. Of course if you compile a very large amount
> >> of software every day, multiple times a day, those less than 2 seconds do
> add up.
> >>
> >> Any suggestion what data I can provide to find the cause of the failure?
> >>
> >> Regards, Frans.
> G.W. Haywood told me he would make a ticket. He also - just as the whole list 
> -
> has the full Testlog.log file since 25/7.
> 
> --- Frans.
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Mark is correct. Clamdscan evaluates the real-path for scans so clamd is 
returning the real path for the scan results.  The test needs to be fixed to 
either not care about the full path and just use the filename, or to evaluate 
the realpath. 

It looked like there may be a second failure in the log Frans attached to his 
earlier email.  The Exclude feature may not be working correctly because of the 
symlink:

E   AssertionError: Unexpected item `b_excluded: 
ClamAV-Test-File.UNOFFICIAL FOUND` which should be absent found in output:
E   
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/TC-gkz19pfu/reload-testfile:
 ClamAV-RELOAD-TestFile.UNOFFICIAL FOUND
E   
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/TC-gkz19pfu/database/reload-test.ndb:
 ClamAV-RELOAD-TestFile.UNOFFICIAL FOUND
E   
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/TC-gkz19pfu/a/a_found:
 ClamAV-Test-File.UNOFFICIAL FOUND
E   
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/TC-gkz19pfu/b/b_excluded:
 ClamAV-Test-File.UNOFFICIAL FOUND
E   
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/TC-gkz19pfu/c/c_found:
 ClamAV-Test-File.UNOFFICIAL FOUND

This is a new test in 0.104 after we fixed a different issue with the Exclude 
feature. I'm not sure though if this is a clamav bug or a test suite bug.  Will 
have to investigate.

-Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> Mark Fortescue via clamav-users
> Sent: Monday, July 26, 2021 4:42 AM
> To: clamav-users@lists.clamav.net
> Cc: Mark Fortescue 
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> Hi Andrew,
> 
> My reading of this small section of the log is that the tests failed because 
> the
> response was not as expected:
> 
>'Wrong reply for command'
> 
> The error seems to be due to the use of a symlink /home/frans/tw/data to
> /mnt/data/fdb-data.
> 
> The tests scripts need to do more work if they are to work properly in the
> presence of symlinks.
> 
> It should be reported as a test suite bug.
> 
> Regards
>   Mark.
> 
> On 26/07/2021 09:43, Andrew C Aitchison via clamav-users wrote:
> > On Mon, 26 Jul 2021, Frans de Boer wrote:
> >
> >>> Here's your problem:
> >>>
> >>> 8<--
> >>> 
> >>> [DEBUG]: Exit code: 1
> >>> [DEBUG]: stdout: Running suite(s): clamd
> >>> 90%: Checks: 77, Failures: 7, Errors: 0
> >>> /home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc
> >>> -org/unit_tests/check_clamd.c:303:F:clamd
> >>> commands:test_basic_commands:15: Wrong reply for command nSCAN
> >>> /home/frans/tw/data/projects/linux/security/clamav/cla
> >>> .
> >>> Received:
> >>> /mnt/data/fdb-data/projects/linux/security/clamav/clamav-
> build/unit_tests/accdenied:
> >>> Access denied. ERROR
> >>>
> >>> Expected:
> >>> /home/frans/tw/data/projects/linux/security/clamav/clamav-
> build/unit_tests/accdenied:
> >>> Access denied. ERROR
> >>>
> >>>
> >>> /home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc
> >>> -org/unit_tests/check_clamd.c:303:F:clamd
> >>> commands:test_basic_commands:16: Wrong reply for command
> nCONTSCAN
> >>> /home/frans/tw/data/projects/linux/security/clamav
> >>> .
> >>> Received:
> >>> /mnt/data/fdb-data/projects/linux/security/clamav/clamav-
> build/unit_tests/accdenied:
> >>> Access denied. ERROR
> >>>
> >>> Expected:
> >>> /home/frans/tw/data/projects/linux/security/clamav/clamav-
> build/unit_tests/accdenied:
> >>> Access denied. ERROR
> >>> 8<--
> >>> 
> >>>
> >>> Are you doing something clever with mount paths, or has the test
> >>> script just not noticed?
> >>>
> >> Nope, nothing 'clever' and doing it already for 20+ years without
> >> problem.
> >> The accdenied file does have the 'r' flag unset, so the error report
> >> is correct.
> >
> > No. IIUC the *test* failed not because the command failed, but because
> > the error message reported the wrong filename.
> >
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

n 7/26/21 8:39 PM, Micah Snyder (micasnyd) via clamav-users wrote:

Frans,

Can you please create a ticket on https://github.com/Cisco-Talos/clamav/issues 
for the clamd test failure? Please attach the verbose output from running:
   ctest -V

Regarding make -j [n] vs ninja -- yes it's not a huge difference.  It's just a 
convenience if you're compiling a lot.  We should probably remove the ninja 
suggestion from the INSTALL.md file.
I didn't include it in 
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html
We do mention it here, which is good enough: 
https://docs.clamav.net/manual/Development/development-builds.html

-Micah


-Original Message-
From: clamav-users  On Behalf Of
Frans de Boer
Sent: Sunday, July 25, 2021 11:08 AM
To: clamav-users@lists.clamav.net
Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
is here!

I get things compiled etc., but testing clamd keeps on failing. I tried three
different machines/CPU's to no avail.

I use OpenSUSE Tumbleweed with newest cmake etc.

One remark: using 'make -j [n]' instead of ninja only takes less than 2 seconds
longer to build things. So, the 'big speed up' is only a 'very minor speed up'. 
Of
course if you compile a very large amount of software every day, multiple times
a day, those less than 2 seconds do add up.

Any suggestion what data I can provide to find the cause of the failure?

Regards, Frans.
G.W. Haywood told me he would make a ticket. He also - just as the whole 
list - has the full Testlog.log file since 25/7.


--- Frans.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Frans,

Can you please create a ticket on https://github.com/Cisco-Talos/clamav/issues 
for the clamd test failure? Please attach the verbose output from running:
  ctest -V

Regarding make -j [n] vs ninja -- yes it's not a huge difference.  It's just a 
convenience if you're compiling a lot.  We should probably remove the ninja 
suggestion from the INSTALL.md file.
I didn't include it in 
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html 
We do mention it here, which is good enough: 
https://docs.clamav.net/manual/Development/development-builds.html

-Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> Frans de Boer
> Sent: Sunday, July 25, 2021 11:08 AM
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> I get things compiled etc., but testing clamd keeps on failing. I tried three
> different machines/CPU's to no avail.
> 
> I use OpenSUSE Tumbleweed with newest cmake etc.
> 
> One remark: using 'make -j [n]' instead of ninja only takes less than 2 
> seconds
> longer to build things. So, the 'big speed up' is only a 'very minor speed 
> up'. Of
> course if you compile a very large amount of software every day, multiple 
> times
> a day, those less than 2 seconds do add up.
> 
> Any suggestion what data I can provide to find the cause of the failure?
> 
> Regards, Frans.
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Rick Cooper]

And what, exactly, is the reason for moving to cmake? I am sure you know
it's going to be problematic for thousands of people so I am curious what
tremendous gain of speed, size, memory usage or seciurity the other users
get from this change, or if it's just a convenience thing for the
developers?
 
 

  _  

From: clamav-users [mailto:clamav-users-boun...@lists.clamav.net] On Behalf
Of Joel Esler (jesler) via clamav-users
Sent: Thursday, July 22, 2021 12:19 PM
To: ClamAV users ML; ClamAV Development
Cc: Joel Esler (jesler)
Subject: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is
here!





https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html



ClamAV 0.104.0 Release Candidate is here!


We are pleased to announce the ClamAV 0.104.0 release
<https://www.clamav.net/downloads> candidate.

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> , or on our Discord
<https://discord.gg/sGaxA5Q> , which is bridged with our IRC.

This release candidate phase is only expected to last about two to four
weeks before the 0.104.0 Stable version will be published. Take this
opportunity to verify that you 0.104.0 can build and run in your
environment.  

Please submit bug reports to the ClamAV
<https://github.com/Cisco-Talos/clamav/issues> project GitHub Issues.   

ClamAV 0.104.0 includes the following improvements and changes.


 
<https://github.com/Cisco-Talos/clamav/blob/dev/0.104/NEWS.md#new-requiremen
ts> 


New Requirements


*   
As of ClamAV 0.104, CMake is required to build ClamAV.

*   We have added comprehensive build instructions for using CMake to
the new INSTALL.md file. The online documentation will also be updated to
include CMake build instructions. 

*   The Autotools and the Visual Studio build systems have been removed.


 
<https://github.com/Cisco-Talos/clamav/blob/dev/0.104/NEWS.md#major-changes>



Major changes


*   
The built-in LLVM for the bytecode runtime has been removed.

*   The bytecode interpreter is the default runtime for bytecode
signatures just as it was in ClamAV 0.103. 

*   We wished to add support for newer versions of LLVM, but ran out of
time. If you're building ClamAV from source and you wish to use LLVM instead
of the bytecode interpreter, you will need to supply the development
libraries for LLVM version 3.6.2. See INSTALL.md to learn more. 

*   
There are now official ClamAV images on Docker Hub.

*   Note: Until ClamAV 0.104.0 is released, these images are limited to
"unstable" versions, which are updated daily with the latest changes in the
default branch on GitHub.

You can find the images on Docker Hub under
<https://hub.docker.com/r/clamav/clamav> clamav.

Docker Hub ClamAV tags:

*   
clamav/clamav:: A release preloaded with signature databases.

Using this container will save the ClamAV project some bandwidth.
Use this if you will keep the image around so that you don't download the
entire database set every time you start a new container. Updating with
FreshClam from the existing databases set does not use much data.

*   
clamav/clamav:_base: A release with no signature databases.

Use this container only if you mount a volume in your container
under /var/lib/clamav to persist your signature database databases. This
method is the best option because it will reduce data costs for ClamAV and
for the Docker registry, but it does require advanced familiarity with Linux
and Docker.

Caution: Using this image without mounting an existing database
directory will cause FreshClam to download the entire database set each time
you start a new container.

You can use the unstable version (i.e. clamav/clamav:unstable or
clamav/clamav:unstable_base) to try the latest from our development branch.

Please, be kind when using "free" bandwidth for the virus databases and
Docker registry. Try not to download the entire database set or the larger
ClamAV database images on a regular basis.

For more details, see the ClamAV Docker
<https://docs.clamav.net/manual/Installing/Docker.html> documentation.

Special thanks to Olliver Schinagl for his excellent work creating ClamAV's
new Docker files, image database deployment tooling, and user documentation.

*   
clamd and freshclam are now available as Windows services. To install and
run them, use the --install-service option and net start [name] command.

Special thanks to Gianluigi Tiesi for his original work on this
feature.


 
<https://github.com/Cisco-Talos/clamav/blob/dev/0.104/NEWS.md#notable-change
s> 


Notable changes


We added these features in 0.103.1 but wanted to re-post them here, as patch
versions do not generally introduce new options:

*   
Added a new scan option to alert on broken media (

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Mark Fortescue via clamav-users]

Hi Andrew,

My reading of this small section of the log is that the tests failed 
because the response was not as expected:


  'Wrong reply for command'

The error seems to be due to the use of a symlink /home/frans/tw/data to 
/mnt/data/fdb-data.


The tests scripts need to do more work if they are to work properly in 
the presence of symlinks.


It should be reported as a test suite bug.

Regards
Mark.

On 26/07/2021 09:43, Andrew C Aitchison via clamav-users wrote:

On Mon, 26 Jul 2021, Frans de Boer wrote:


Here's your problem:

8<--
[DEBUG]: Exit code: 1
[DEBUG]: stdout: Running suite(s): clamd
90%: Checks: 77, Failures: 7, Errors: 0
/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:15: Wrong reply for command nSCAN 
/home/frans/tw/data/projects/linux/security/clamav/cla

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR



/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:16: Wrong reply for command nCONTSCAN 
/home/frans/tw/data/projects/linux/security/clamav

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR

8<--

Are you doing something clever with mount paths, or has the test
script just not noticed?

Nope, nothing 'clever' and doing it already for 20+ years without 
problem.
The accdenied file does have the 'r' flag unset, so the error report 
is correct.


No. IIUC the *test* failed not because the command failed,
but because the error message reported the wrong filename.



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

On 7/26/21 10:42 AM, G.W. Haywood via clamav-users wrote:

Hi there,

On Mon, 26 Jul 2021, Frans de Boer wrote:


On 7/26/21 9:41 AM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


On 7/25/21 8:44 PM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


I get things compiled etc., but testing clamd keeps on failing. ...
...
Any suggestion what data I can provide to find the cause of the 
failure?


The output from the tests would probably be a good start.


The output in TestLog.log


Here's your problem:

8<-- 



Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR

...
8<-- 



Are you doing something clever with mount paths, or has the test
script just not noticed?

Nope, nothing 'clever' and doing it already for 20+ years without 
problem.
The accdenied file does have the 'r' flag unset, so the error report 
is correct.


Then it looks like a problem in the test suite, which is complaining
that the expected paths aren't the same even though it's the same file
and the correct result for the file.  It seems clear that clamd itself
is working OK, I'd ignore it and file a report on Bugzilla.


Ok, thnx for your reply.

Frans.

--
A: Yes, just like thatA: Ja, net zo
Q: Oh, Just like reading a book backwards Q: Oh, net als een boek 
achterstevoren lezen
A: Because it upsets the natural flow of a story  A: Omdat het de natuurlijke 
gang uit het verhaal haalt
Q: Why is top-posting annoying?   Q: Waarom is Top-posting zo 
irritant?


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Andrew C Aitchison via clamav-users]

On Mon, 26 Jul 2021, Frans de Boer wrote:


Here's your problem:

8<--
[DEBUG]: Exit code: 1
[DEBUG]: stdout: Running suite(s): clamd
90%: Checks: 77, Failures: 7, Errors: 0
/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:15: Wrong reply for command nSCAN 
/home/frans/tw/data/projects/linux/security/clamav/cla

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR



/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:16: Wrong reply for command nCONTSCAN 
/home/frans/tw/data/projects/linux/security/clamav

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR

8<--

Are you doing something clever with mount paths, or has the test
script just not noticed?


Nope, nothing 'clever' and doing it already for 20+ years without problem.
The accdenied file does have the 'r' flag unset, so the error report is 
correct.


No. IIUC the *test* failed not because the command failed,
but because the error message reported the wrong filename.

--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Mon, 26 Jul 2021, Frans de Boer wrote:


On 7/26/21 9:41 AM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


On 7/25/21 8:44 PM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


I get things compiled etc., but testing clamd keeps on failing. ...
...
Any suggestion what data I can provide to find the cause of the failure?


The output from the tests would probably be a good start.


The output in TestLog.log


Here's your problem:

8<--

Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR

...
8<--

Are you doing something clever with mount paths, or has the test
script just not noticed?


Nope, nothing 'clever' and doing it already for 20+ years without problem.
The accdenied file does have the 'r' flag unset, so the error report is 
correct.


Then it looks like a problem in the test suite, which is complaining
that the expected paths aren't the same even though it's the same file
and the correct result for the file.  It seems clear that clamd itself
is working OK, I'd ignore it and file a report on Bugzilla.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

On 7/26/21 9:41 AM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


On 7/25/21 8:44 PM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


I get things compiled etc., but testing clamd keeps on failing. ...
...
Any suggestion what data I can provide to find the cause of the 
failure?


The output from the tests would probably be a good start.


The output in TestLog.log


Here's your problem:

8<--
[DEBUG]: Exit code: 1
[DEBUG]: stdout: Running suite(s): clamd
90%: Checks: 77, Failures: 7, Errors: 0
/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:15: Wrong reply for command nSCAN 
/home/frans/tw/data/projects/linux/security/clamav/cla

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR



/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd 
commands:test_basic_commands:16: Wrong reply for command nCONTSCAN 
/home/frans/tw/data/projects/linux/security/clamav

.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: 
Access denied. ERROR

8<--

Are you doing something clever with mount paths, or has the test
script just not noticed?


Nope, nothing 'clever' and doing it already for 20+ years without problem.
The accdenied file does have the 'r' flag unset, so the error report is 
correct.


--- Frans

--
A: Yes, just like thatA: Ja, net zo
Q: Oh, Just like reading a book backwards Q: Oh, net als een boek 
achterstevoren lezen
A: Because it upsets the natural flow of a story  A: Omdat het de natuurlijke 
gang uit het verhaal haalt
Q: Why is top-posting annoying?   Q: Waarom is Top-posting zo 
irritant?


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


On 7/25/21 8:44 PM, G.W. Haywood via clamav-users wrote:

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


I get things compiled etc., but testing clamd keeps on failing. ...
...
Any suggestion what data I can provide to find the cause of the failure?


The output from the tests would probably be a good start.


The output in TestLog.log


Here's your problem:

8<--
[DEBUG]: Exit code: 1
[DEBUG]: stdout: Running suite(s): clamd
90%: Checks: 77, Failures: 7, Errors: 0
/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd
 commands:test_basic_commands:15: Wrong reply for command nSCAN 
/home/frans/tw/data/projects/linux/security/clamav/cla
.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: Access denied. ERROR



/home/frans/tw/data/projects/linux/security/clamav/clamav-0.104.0-rc-org/unit_tests/check_clamd.c:303:F:clamd
 commands:test_basic_commands:16: Wrong reply for command nCONTSCAN 
/home/frans/tw/data/projects/linux/security/clamav
.
Received: 
/mnt/data/fdb-data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: Access denied. ERROR


Expected: 
/home/frans/tw/data/projects/linux/security/clamav/clamav-build/unit_tests/accdenied: Access denied. ERROR

8<--

Are you doing something clever with mount paths, or has the test
script just not noticed?

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Arjen de Korte via clamav-users]

Citeren Frans de Boer :


On 7/25/21 8:50 PM, Arjen de Korte via clamav-users wrote:

Citeren Frans de Boer :

I get things compiled etc., but testing clamd keeps on failing. I  
tried three different machines/CPU's to no avail.


I use OpenSUSE Tumbleweed with newest cmake etc.


I have an experimental version available in  
https://build.opensuse.org/package/show/home:adkorte/clamav


It seems to work OK, but use at own risk.

Hi Arjen,

I downloaded the ..242.src.rpm archive and extracted the  
104.0.tar.gz file from it. Same error.


Unsurprising. This is the same sourcefile from upstream, but you'll  
need to make quite some changes in the .spec file in order to build  
it. If you used the same .spec file, you'll get the same results.


It is probably easier to either install the .src.rpm and build locally  
from the .spec file in it, or add the repository where it is from so  
you can just install the .rpm files without building yourself  
(https://download.opensuse.org/repositories/home:/adkorte/openSUSE_Tumbleweed/home:adkorte.repo)


However, there are other files in that archive too, if I need them,  
how to do so?


--- Frans.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml





___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

On 7/25/21 8:50 PM, Arjen de Korte via clamav-users wrote:

Citeren Frans de Boer :

I get things compiled etc., but testing clamd keeps on failing. I 
tried three different machines/CPU's to no avail.


I use OpenSUSE Tumbleweed with newest cmake etc.


I have an experimental version available in 
https://build.opensuse.org/package/show/home:adkorte/clamav


It seems to work OK, but use at own risk. 

Hi Arjen,

I downloaded the ..242.src.rpm archive and extracted the 104.0.tar.gz 
file from it. Same error.
However, there are other files in that archive too, if I need them, how 
to do so?


--- Frans.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Arjen de Korte via clamav-users]

Citeren Frans de Boer :

I get things compiled etc., but testing clamd keeps on failing. I  
tried three different machines/CPU's to no avail.


I use OpenSUSE Tumbleweed with newest cmake etc.


I have an experimental version available in  
https://build.opensuse.org/package/show/home:adkorte/clamav


It seems to work OK, but use at own risk.


___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Arjen de Korte via clamav-users]

Citeren Arjen de Korte via clamav-users :


[6s] -- Performing Test Iconv_IS_BUILT_IN
[6s] -- Performing Test Iconv_IS_BUILT_IN - Failed
[6s] CMake Error at  
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230  
(message):

[6s]   Could NOT find Iconv (missing: Iconv_LIBRARY)
[6s] Call Stack (most recent call first):
[6s]
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594  
(_FPHSA_FAILURE_MESSAGE)

[6s]   cmake/FindIconv.cmake:129 (find_package_handle_standard_args)
[6s]   CMakeLists.txt:332 (find_package)


Apparently this test is not able to determine if iconv is actually  
built-in. Adding '-D Iconv_IS_BUILT_IN=ON' to the cmake command line,  
fixes this. If this is the intended behavior, it might be useful to  
change the error message (it took me a while to figure out that iconv  
was actually built-in).


Another thing is that when adding '-D ENABLE_UNRAR=OFF' to the cmake  
command line, one also has to set '-D ENABLE_TESTS=OFF', otherwise the  
build will fail fairly quickly due to the following error.


Error evaluating generator expression:

  $

No target "ClamAV::libunrar_iface"

errors. Not sure if this is expected though.

Other than this, the build seems to succeed on openSUSE Tumbleweed and  
the resulting binaries seem to run fine.



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Sun, 25 Jul 2021, Frans de Boer wrote:


I get things compiled etc., but testing clamd keeps on failing. ...
...
Any suggestion what data I can provide to find the cause of the failure?


The output from the tests would probably be a good start.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Frans de Boer]

I get things compiled etc., but testing clamd keeps on failing. I tried 
three different machines/CPU's to no avail.


I use OpenSUSE Tumbleweed with newest cmake etc.

One remark: using 'make -j [n]' instead of ninja only takes less than 2 
seconds longer to build things. So, the 'big speed up' is only a 'very 
minor speed up'. Of course if you compile a very large amount of 
software every day, multiple times a day, those less than 2 seconds do 
add up.


Any suggestion what data I can provide to find the cause of the failure?

Regards, Frans.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Arjen de Korte via clamav-users]

Citeren "Gary R. Schmidt" :


On 24/07/2021 17:01, Gary R. Schmidt wrote:

[SNIP]

Next I will try with GCC/G++, wonder where it will fail...


[ snip ]

Fails for me in pretty much the same way on Linux:

[4s] -- The C compiler identification is GNU 11.1.1
[4s] -- The CXX compiler identification is GNU 11.1.1
[4s] -- Detecting C compiler ABI info
[4s] -- Detecting C compiler ABI info - done
[4s] -- Check for working C compiler: /usr/bin/cc - skipped
[4s] -- Detecting C compile features
[4s] -- Detecting C compile features - done
[4s] -- Detecting CXX compiler ABI info
[4s] -- Detecting CXX compiler ABI info - done
[4s] -- Check for working CXX compiler: /usr/bin/c++ - skipped
[4s] -- Detecting CXX compile features
[4s] -- Detecting CXX compile features - done
[4s] -- Could NOT find Git (missing: GIT_EXECUTABLE)
[5s] -- Found Libcheck: /usr/include
[5s] -- Found Python3: /usr/bin/python3.8 (found version "3.8.10")  
found components: Interpreter

[5s] -- Valgrind not found.
[6s] -- Found Threads: TRUE
[6s] -- Found OpenSSL: /usr/lib64/libcrypto.so (found version "1.1.1k")
[6s] -- Found ZLIB: /usr/lib64/libz.so (found version "1.2.11")
[6s] -- Found BZip2: /usr/lib64/libbz2.so (found version "1.0.8")
[6s] -- Looking for BZ2_bzCompressInit
[6s] -- Looking for BZ2_bzCompressInit - found
[6s] -- Found LibXml2: /usr/lib64/libxml2.so (found version "2.9.12")
[6s] -- Found PCRE2: /usr/lib64/libpcre2-8.so
[6s] -- Performing Test Iconv_IS_BUILT_IN
[6s] -- Performing Test Iconv_IS_BUILT_IN - Failed
[6s] CMake Error at  
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230  
(message):

[6s]   Could NOT find Iconv (missing: Iconv_LIBRARY)
[6s] Call Stack (most recent call first):
[6s]
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594  
(_FPHSA_FAILURE_MESSAGE)

[6s]   cmake/FindIconv.cmake:129 (find_package_handle_standard_args)
[6s]   CMakeLists.txt:332 (find_package)



___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Hi Gary, Ged,

Sorry no we don't test on Solaris anymore. To be frank, it seems pretty clear 
that Oracle isn't maintaining Solaris anymore.  All of the packages are years 
out of date, even the opencsw ones. It simply wasn't worth the effort to 
maintain the solaris 10 and 11 vms we used to test with.
Our list of systems that we test on is 
https://docs.clamav.net/#supported-platforms

Ged: I also have a Raspberry Pi (3b) running the latest Raspberry Pi OS. I 
configured it to do daily clamav build tests with buildkite: 
https://buildkite.com/clamav/clamav-public-tests
I know what you mean about it crashing. Before I added a heat sink I was able 
to get it to overheat & crash pretty easily.  I’m told the Pi 4 really needs 
extra cooling.  Still, after seeing that you can rack mount a bunch of these 
things and set them up as a cluster, it's awfully tempting to give it a try.

Gary, if you want to set the CLFAGS and LDFLAGS, you should be able to do this 
before you run cmake:

export CFLAGS="-m32 -I/opt/local/include"
export CXXFLAGS="-m32 -I/opt/local/include"
export LDFLAGS="-m32 -L/opt/local/lib -R/opt/local/lib"

The `-D SOME_VARIABLE` thing is just for CMake variables, which is why you saw:

CMake Warning:
   Manually-specified variables were not used by the project:

 CXXFLAGS
 LDFLAGS

I also noticed you set the include path for libpcre2 but not the library path. 
In the configuration summary it did find libpcre2 but in /usr/lib instead of 
/opt/local
https://github.com/Cisco-Talos/clamav/blob/239ede802387ec89b25502b2f8bb0fee0778728f/INSTALL.md#libpcre2

We didn't implement a `make distclean` equivalent. Instead (and I recommend 
doing this with autotools anyways), do your builds in a different directory 
than the source. I recommend using a subdirectory named "build". Then if 
something goes wrong, you can `rm -rf ../build/*` (note I now use ../build/* 
after accidentally running it with ../* in my home directory! So 
embarrassing...).
Or if you're using Git, you can do `git clean -fdx` to remove anything that's 
not in version control.

We of don't have any Solaris instructions, there are instructions for other 
systems here: 
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html#build-clamav

Disclaimer: We're (rather slowly) working on integrating Rust programming 
language support into our build system so we can rewrite some components or 
write new components in Rust. We'd planned on adding this in 0.104, but it got 
pushed back to 0.105. For 99% of people that just means the Rust toolchain will 
have to be installed to do the build. The build instructions won't change any 
and CMake will take care of everything. 
But Solaris (x86 and sparc) are Tier 2 platforms for Rust support, meaning you 
can only cross compile Rust code for Solaris. 
https://doc.rust-lang.org/nightly/rustc/platform-support.html 
So I don't expect building clamav for Solaris will be easy (if possible) once 
we add the Rust toolchain requirement.

Regards,
Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> G.W. Haywood via clamav-users
> Sent: Saturday, July 24, 2021 5:51 AM
> To: ClamAV users ML 
> Cc: G.W. Haywood ; ClamAV Development
> 
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> Hi there,
> 
> On Sat, 24 Jul 2021, Gary R. Schmidt wrote:
> 
> > On 24/07/2021 17:01, Gary R. Schmidt wrote:
> >> [SNIP]
> >>
> >> Next I will try with GCC/G++, wonder where it will fail...
> > ...
> > CMake Error at
> > /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137
> > (message):
> >  Could NOT find Iconv (missing: Iconv_LIBRARY) Call Stack (most recent
> > call first):
> >  /usr/share/cmake-
> 3.15/Modules/FindPackageHandleStandardArgs.cmake:378
> > (_FPHSA_FAILURE_MESSAGE)
> 
> Ouch.  Looks like you're having even more trouble than I did.  Well, that's 
> what
> release candidates (and we) are here for. :)  Can't help much with Solaris, 
> sorry,
> but doesn't Micah build on it too?
> 
> > Oh, by the way, how do you tell CMake to wipe out its effects and go
> > back to a virginal environment, a la "make distclean"???
> 
> According to 'man cmake' there's a command line option
> 
> --clean-first
> 
> which might do what you want (I've never used it, this cmake stuff is all new 
> to
> me) and in the top of the source tree I *think* you can
> 
> rm -rf ./build
> 
> However I always
> 
> rm -rf /home/me/clamav-0
> 
> even if I'm using 'make'.
> 
> --
> 
> 73,
> Ged.
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/cl

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Gary R. Schmidt]

On 24/07/2021 22:51, G.W. Haywood via clamav-users wrote:

Hi there,

On Sat, 24 Jul 2021, Gary R. Schmidt wrote:


On 24/07/2021 17:01, Gary R. Schmidt wrote:

[SNIP]

Next I will try with GCC/G++, wonder where it will fail...

...
CMake Error at 
/usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
(message):

 Could NOT find Iconv (missing: Iconv_LIBRARY)
Call Stack (most recent call first):
 /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)


Ouch.  Looks like you're having even more trouble than I did.  Well,
that's what release candidates (and we) are here for. :)  Can't help
much with Solaris, sorry, but doesn't Micah build on it too?

I do recall that it used to be in the build farm, but I think that 
stopped a while ago.



Oh, by the way, how do you tell CMake to wipe out its effects and go
back to a virginal environment, a la "make distclean"???


According to 'man cmake' there's a command line option

--clean-first


That only works if there is a "clean" target available.  :-(

[SNIP]


However I always

rm -rf /home/me/clamav-0

even if I'm using 'make'.

Yes, I've been doing that, but just wondered if there was some logic 
built-in (or added).  :-)


Cheers,
GaryB-)

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Sat, 24 Jul 2021, Gary R. Schmidt wrote:


On 24/07/2021 17:01, Gary R. Schmidt wrote:

[SNIP]

Next I will try with GCC/G++, wonder where it will fail...

...
CMake Error at 
/usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
(message):

 Could NOT find Iconv (missing: Iconv_LIBRARY)
Call Stack (most recent call first):
 /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)


Ouch.  Looks like you're having even more trouble than I did.  Well,
that's what release candidates (and we) are here for. :)  Can't help
much with Solaris, sorry, but doesn't Micah build on it too?


Oh, by the way, how do you tell CMake to wipe out its effects and go
back to a virginal environment, a la "make distclean"???


According to 'man cmake' there's a command line option

--clean-first

which might do what you want (I've never used it, this cmake stuff is
all new to me) and in the top of the source tree I *think* you can

rm -rf ./build

However I always

rm -rf /home/me/clamav-0

even if I'm using 'make'.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Gary R. Schmidt]

On 24/07/2021 17:01, Gary R. Schmidt wrote:

[SNIP]

Next I will try with GCC/G++, wonder where it will fail...


-- The C compiler identification is GNU 10.2.0
-- The CXX compiler identification is GNU 10.2.0
-- Check for working C compiler: /bin/gcc
-- Check for working C compiler: /bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /bin/c++
-- Check for working CXX compiler: /bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /bin/git (found version "2.30.2")
-- Found Libcheck: /usr/include
-- Found Python3: /bin/python3.7 (found version "3.7.10") found 
components:  Interpreter
Python 3 package 'pytest' is not installed for /bin/python3.7 and is not 
available in your PATH.

Failed unit tests will be easier to read if you install pytest.
Eg:  python3 -m pip install --user pytest
-- Found Threads: TRUE
-- Found OpenSSL: /opt/local/lib/libcrypto.so
-- Found ZLIB: /usr/lib/64/libz.so (found version "1.2.11")
-- Found BZip2: /usr/lib/64/libbz2.so (found version "1.0.8")
-- Looking for BZ2_bzCompressInit
-- Looking for BZ2_bzCompressInit - found
-- Found LibXml2: /usr/lib/64/libxml2.so (found version "2.9.9")
-- Found PCRE2: /usr/lib/64/libpcre2-8.so
-- Performing Test Iconv_IS_BUILT_IN
-- Performing Test Iconv_IS_BUILT_IN - Failed
CMake Error at 
/usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
(message):

  Could NOT find Iconv (missing: Iconv_LIBRARY)
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)


Nice and early...

Oh, by the way, how do you tell CMake to wipe out its effects and go 
back to a virginal environment, a la "make distclean"???


Cheers,
GaryB-)

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Gary R. Schmidt]

On 23/07/2021 02:18, Joel Esler (jesler) via clamav-users wrote:




https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html 




  ClamAV 0.104.0 Release Candidate is here!



Well, first try on Solaris 11.4 doesn't want to work.

I had hopes that CMake would be better than autotools, but so far I am 
decidedly unimpressed.


The flags I'm passing are guesses, except where taken from INSTALL.md.

Here we go, sorry for the huge post:
Input:
cmake   -D CMAKE_INSTALL_PREFIX:PATH=/opt/sandbox \
-D PCRE2_INCLUDE_DIR=/opt/local/include \
-D ENABLE_MILTER=OFF \
-D OPENSSL_ROOT_DIR=/opt/local/ssl \
-D OPENSSL_INCLUDE_DIR=/opt/local/include/openssl \
-D OPENSSL_CRYPTO_LIBRARY=/opt/local/lib/libcrypto.so \
-D OPENSSL_SSL_LIBRARY=/opt/local/lib/libssl.so \
-D CFLAGS="-m32 -I/opt/local/include" \
-D CXXFLAGS="-m32 -I/opt/local/include" \
-D LDFLAGS="-m32 -L/opt/local/lib -R/opt/local/lib"

cmake --build . --target install --config Release
Output:

CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


-- The C compiler identification is SunPro 5.15.0
-- The CXX compiler identification is SunPro 5.15.0
-- Check for working C compiler: /opt/developerstudio12.6/bin/cc
-- Check for working C compiler: /opt/developerstudio12.6/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /opt/developerstudio12.6/bin/CC
-- Check for working CXX compiler: /opt/developerstudio12.6/bin/CC -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /bin/git (found version "2.30.2")
-- Found Libcheck: /usr/include
-- Found Python3: /bin/python3.7 (found version "3.7.10") found 
components:  Interpreter
Python 3 package 'pytest' is not installed for /bin/python3.7 and is not 
available in your PATH.

Failed unit tests will be easier to read if you install pytest.
Eg:  python3 -m pip install --user pytest
-- Found Threads: TRUE
-- Found OpenSSL: /opt/local/lib/libcrypto.so
-- Found ZLIB: /usr/lib/libz.so (found version "1.2.11")
-- Found BZip2: /usr/lib/libbz2.so (found version "1.0.8")
-- Looking for BZ2_bzCompressInit
-- Looking for BZ2_bzCompressInit - found
-- Found LibXml2: /usr/lib/libxml2.so (found version "2.9.9")
-- Found PCRE2: /usr/lib/libpcre2-8.so
-- Performing Test Iconv_IS_BUILT_IN
-- Performing Test Iconv_IS_BUILT_IN - Success
-- Found Iconv: /usr/lib/libc.so
-- Found JSONC: /usr/lib/libjson-c.so
-- Found CURL: /usr/lib/libcurl.so (found version "7.74.0-DEV")
-- Found CURSES: /usr/lib/libcurses.so
-- Performing Test CXX_FLAG__std_c_14
-- Performing Test CXX_FLAG__std_c_14 - Failed
-- Performing Test CXX_FLAG__std_c_11
-- Performing Test CXX_FLAG__std_c_11 - Failed

[SNIP bunch of stuff...]

-- Performing Test C_FLAG__Wall
-- Performing Test C_FLAG__Wall - Success
-- Performing Test C_FLAG__Wextra
-- Performing Test C_FLAG__Wextra - Success
-- Performing Test C_FLAG__Wformat_security
-- Performing Test C_FLAG__Wformat_security - Success
-- Performing Test CXX_FLAG__Wall
-- Performing Test CXX_FLAG__Wall - Success
-- Performing Test CXX_FLAG__Wformat_security
-- Performing Test CXX_FLAG__Wformat_security - Success
-- Performing Test HAVE_MMAP
-- Performing Test HAVE_MMAP - Success
-- Performing Test HAVE_MMAP_MAP_ANONYMOUS
-- Performing Test HAVE_MMAP_MAP_ANONYMOUS - Success
-- Performing Test HAVE_SYSCONF_SC_PAGESIZE
-- Performing Test HAVE_SYSCONF_SC_PAGESIZE - Success
-- Configuration Options Summary --
[Deleted annoying ANSI escape sequences.]
Package Version:ClamAV 0.104.0-rc
libclamav version:  10:0:1
libfreshclam version:   2:2:0
Install prefix: /opt/sandbox
Install database dir:   /opt/sandbox/share/clamav
Install config dir: /opt/sandbox/etc
Host system:SunOS-5.11
Target system:  SunOS-5.11
Compiler:
Build type: RelWithDebInfo
C compiler: /opt/developerstudio12.6/bin/cc
C++ compiler:   /opt/developerstudio12.6/bin/CC
CFLAGS: -g -xO2
CXXFLAGS:   -g -xO2
WARNCFLAGS:  -Wall -Wextra -Wformat-security
Build Options:
Build apps: ON
Shared library: ON
Static library: OFF
Enable UnRAR:   ON
Examples:   OFF
Tests:  ON
Build man pages:ON
Build doxygen HTML: OFF
Build Extras:
Build milter:   OFF  (toggle with -DENABLE_MILTER=ON/OFF)
-- Engine Options --
 

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi Micah,

On Fri, 23 Jul 2021, Micah Snyder (micasnyd) via clamav-users wrote:


I'm sad to hear how much effort it was to install CMake ...


It's the sort of thing that happens with computers. :/


... very surprised to hear that it crashed your machine.


To be fair it's not hard to crash a Raspberry Pi4B.  They're not at
all like the earlier models.  The 3B+ that I use for my desktop has
always been a lot more reliable.  Frankly if I knew three years ago
what I know about them now I'd have been against getting them, but a
lot of effort is invested into making them work and they pretty much
do what's needed of them for a power consumption of a few percent of
that used by the boxes they replaced.  Things like AMD Opterons can
use more power than a Pi just for the cooling fans.  Our Pis don't
have cooling fans.


... Which os/distro/arch are you using?


Linux, Raspbian (as near as dammit Debian), armhf.  Raspberry Pi4B,
4G RAM, all storage is NFS mounted over 1Gbit/s Ethernet.


You mention Debian Stretch (9) ...


That was then.  Now it's Buster (10).  In case it matters, I built
cmake just for the user which builds the ClamAV binaries, it wasn't a
system-wide install.  I didn't build these systems myself; I just did
the mail stuff, and I didn't want to break anything which might want
to use the system's cmake - I don't even know if anything does.


... in a new docker debian:9 container it takes 2.971 seconds ...
   real0m5.178s
   user0m2.971s


Well 5.178 seconds by the wall clock, but that was still over 3,600
times faster!


You're right that milter is required by default now.  The approach
with the old build system was so the optional stuff would be skipped
if you didn't have it. ... we ...  don't test the project in every
variation ...  users should still be able to expect that a default
build gives them all the features.


All understood.  To me it seems like a lot of big steps all at once
with a project that has so many users with such a wide variety of
systems, use cases and and skill sets but I guess we'll get to know
more about that when the 0.104 release actually hits the fan. :)


... you can use `-D ENABLE_MILTER=OFF` and then skip the milter ...


Sure, I saw that in the docs but didn't want to throw any more
spanners into the works than I had there already.  Normally I don't
build the milter because the clamd server doesn't run an MTA, my
own milters run on the mail servers and handle the communications
with the clamd server.


Sorry I really have zero interest in bringing back and update
Autotools for 0.104.  For what it's worth, we do plan to publish a
clamav 0.103.4 patch version alongside an 0.104.1 version in
probably 2 months (give or take).  Depending on how 0.104 adoption
goes, we could have an 0.103.5 version as well, but I don’t expect
that we will.


It doesn't matter to me of course, now that I've built a version of
cmake which can build ClamAV, but going back to the numbers of users
and the variety of systems I just wonder if it's going to cause you
pain further down the line.

Thanks for the help and thoughts, and good luck with 0.104. :)

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Hi Ged,

I'm sad to hear how much effort it was to install CMake on your machine, and 
very surprised to hear that it crashed your machine. 
On most x86 and amd64 distributions, the `pip3 install cmake` step takes a few 
seconds because it is precompiled. Which os/distro/arch are you using? 
You mention Debian Stretch (9). The package from apt-get is version 3.7.2 which 
is definitely too old. But using pip3, with Debian Stretch in a new docker 
debian:9 container it takes 2.971 seconds to install:

root@9e6c4f667db4:/# time pip3 install cmake
Collecting cmake
  Downloading 
https://files.pythonhosted.org/packages/2e/e6/988e201a5fea43dafcdcfd7b4b8e971c0adf22ee554cd1fa1a84237ea41a/cmake-3.21.0-py2.py3-none-manylinux_2_5_x86_64.manylinux1_x86_64.whl
 (19.8MB)
100% || 19.8MB 109kB/s
Installing collected packages: cmake
Successfully installed cmake-3.21.0

real0m5.178s
user0m2.971s
sys 0m0.602s
root@9e6c4f667db4:/#

You're right that milter is required by default now.  The approach with the old 
build system was so the optional stuff would be skipped if you didn't have it.  
- No libbz2? No support for bzip2.
- No libxml2? No support for DMG, DOCX, MHTML, and other types that use XML.
- No pcre or pcre2 library? Some regexes won't work.
Etc. 

Personally I don't think this is acceptable. I don't trust everyone to remember 
to install the "optional" dependencies, and we certainly don't test the project 
in every variation with some or all of the (previously) optional dependencies 
omitted.  I wouldn't be surprised if there are crashes with some features 
disabled. 

I accept that requiring milter by default doesn't quite fall into the same 
category in that it won't cause clamscan failures, or false negatives or 
anything. But I think users should still be able to expect that a default build 
gives them all the features. But I mostly don't want to deal with a situation 
where a user on distribution-X can't find clamsubmit because the package 
maintainer accidentally installed libjson-c instead of libjson-c-devel (just an 
example).  That's my mindset. That's why I chose to make everything required 
for a default CMake build.

If you don't want to build clamav-milter, you can use `-D ENABLE_MILTER=OFF` 
and then skip the milter dependency. 
See the INSTALL.md file for more options: 
https://github.com/Cisco-Talos/clamav/blob/239ede802387ec89b25502b2f8bb0fee0778728f/INSTALL.md#custom-cmake-options

Sorry I really have zero interest in bringing back and update Autotools for 
0.104.
For what it's worth, we do plan to publish a clamav 0.103.4 patch version 
alongside an 0.104.1 version in probably 2 months (give or take).  Depending on 
how 0.104 adoption goes, we could have an 0.103.5 version as well, but I don’t 
expect that we will.

Regards,
Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> G.W. Haywood via clamav-users
> Sent: Friday, July 23, 2021 12:32 PM
> To: Micah Snyder (micasnyd) via clamav-users  us...@lists.clamav.net>
> Cc: G.W. Haywood 
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release
> Candidate is here!
> 
> Hi Micah,
> 
> On Thu, 22 Jul 2021, Micah Snyder (micasnyd) via clamav-users wrote:
> > G.W. Haywood via clamav-users wrote:
> >> On Thu, 22 Jul 2021, Joel Esler (jesler) via clamav-users wrote:
> >>
> >>> ...
> >>> ClamAV 0.104.0 Release Candidate is here!
> >>> ...
> >>>  Please help us validate this release. We need your feedback, so let
> >>> us know what you find ...
> >>
> >> It won't build on Debian Stretch:
> >> ...
> >> CMake 3.14 or higher is required.  You are running version 3.13.4 ...
> >
> > The CMake project has been moving relatively quickly the past few
> > years. We depend on some of the newish features (though they're
> > already up to 3.21 now).  The easiest way to get a newer version of
> > CMake is to install it through Python 3's package manager: pip.
> >
> > I just finished updating the online documentation for building with
> > CMake.  I've included instructions for how to install CMake, using pip
> > if necessary for some systems:
> > https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.
> > html#install-prerequisites
> 
> The first two attempts crashed the machine.  The first after half an hour, the
> second after two hours but by then I was in bed.  I 'time'd the third attempt.
> Five and a half hours.  Well the root partition is on NFS, but even so...
> 8<--
> $ time python3 -m pip install --user cmake Looking in indexes:
> https://pypi.org/simple, https://www.piwheels.org/simple Collecting cmake
&

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi Micah,

On Thu, 22 Jul 2021, Micah Snyder (micasnyd) via clamav-users wrote:

G.W. Haywood via clamav-users wrote:

On Thu, 22 Jul 2021, Joel Esler (jesler) via clamav-users wrote:


...
ClamAV 0.104.0 Release Candidate is here!
...
 Please help us validate this release. We need your feedback, so let
us know what you find ...


It won't build on Debian Stretch:
...
CMake 3.14 or higher is required.  You are running version 3.13.4
...


The CMake project has been moving relatively quickly the past few
years. We depend on some of the newish features (though they're
already up to 3.21 now).  The easiest way to get a newer version of
CMake is to install it through Python 3's package manager: pip.

I just finished updating the online documentation for building with
CMake.  I've included instructions for how to install CMake, using
pip if necessary for some systems:
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html#install-prerequisites


The first two attempts crashed the machine.  The first after half an
hour, the second after two hours but by then I was in bed.  I 'time'd
the third attempt.  Five and a half hours.  Well the root partition is
on NFS, but even so...
8<--
$ time python3 -m pip install --user cmake
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting cmake
  Using cached https://files.pythonhosted.org/.../cmake-3.21.0.tar.gz
  Installing build dependencies ... done
Building wheels for collected packages: cmake
  Running setup.py bdist_wheel for cmake ... done
  Stored in directory: /home/ged/.cache/pip/wheels/56/3b/6e/6f...1d
Successfully built cmake
Installing collected packages: cmake
  ...
Successfully installed cmake-3.21.0

real329m38.416s
user42m44.762s
sys 7m39.186s
8<--


I hope this works for okay for you.


It worked in the end, thanks.  At least it built some executables, I
haven't tried running them and probably won't for the moment as there
are other fish to fry.

It took me about a day to get cmake set up.  Then cmake insisted on
things like libmiter and valgrind by default, which I guess like me
most people probably won't want.  I wonder if you should consider a
reprieve for autotools, at least until the major distros have a cmake
that will build ClamAV, because I think what I had to do would be well
beyond the attention span of most ClamAV users.

When I rebuilt 0.103.3 using autotools to compare with the cmake
build, it somewhat curiously failed to find libmilter although I'd
installed it for the cmake build.  I haven't investigated that yet.

The cmake build was about 20% quicker than using autotools.

HTH

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Micah Snyder (micasnyd) via clamav-users]

Hi Ged,

The CMake project has been moving relatively quickly the past few years. We 
depend on some of the newish features (though they're already up to 3.21 now). 
The easiest way to get a newer version of CMake is to install it through Python 
3's package manager: pip. 

I just finished updating the online documentation for building with CMake.  
I've included instructions for how to install CMake, using pip if necessary for 
some systems: 
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html#install-prerequisites

I hope this works for okay for you.

Regards,
Micah

> -Original Message-
> From: clamav-users  On Behalf Of
> G.W. Haywood via clamav-users
> Sent: Thursday, July 22, 2021 10:16 AM
> To: Joel Esler (jesler) via clamav-users 
> Cc: G.W. Haywood 
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> Hi there,
> 
> On Thu, 22 Jul 2021, Joel Esler (jesler) via clamav-users wrote:
> 
> > ...
> > ClamAV 0.104.0 Release Candidate is here!
> > ...
> >  Please help us validate this release. We need your feedback, so let
> > us know what you find ...
> 
> It won't build on Debian Stretch:
> 
> "~/clamav-0.104.0-rc/build: $ cmake .. -D CMAKE_BUILD_TYPE="Release""
> "CMake Error at CMakeLists.txt:6 (cmake_minimum_required):"
> "CMake 3.14 or higher is required.  You are running version 3.13.4"
> ""
> ""
> "-- Configuring incomplete, errors occurred!"
> 
> Kind of understandable, but rather a shame since the autotools build has been
> junked.  It's time I upgraded to Stretch on the clamd server so I'll look at 
> it
> again after I've found the time to do that.
> 
> Incidentally two '-' signs followed by a space in that error message conflicts
> with the email signature delimiter.  That's why I've quoted the lines in the 
> cut-
> n-paste.
> 
> --
> 
> 73,
> Ged.
> 
> ___
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[G.W. Haywood via clamav-users]

Hi there,

On Thu, 22 Jul 2021, Joel Esler (jesler) via clamav-users wrote:


...
ClamAV 0.104.0 Release Candidate is here!
...
 Please help us validate this release. We need your feedback, so let
us know what you find ...


It won't build on Debian Stretch:

"~/clamav-0.104.0-rc/build: $ cmake .. -D CMAKE_BUILD_TYPE="Release""
"CMake Error at CMakeLists.txt:6 (cmake_minimum_required):"
"CMake 3.14 or higher is required.  You are running version 3.13.4"
""
""
"-- Configuring incomplete, errors occurred!"

Kind of understandable, but rather a shame since the autotools build
has been junked.  It's time I upgraded to Stretch on the clamd server
so I'll look at it again after I've found the time to do that.

Incidentally two '-' signs followed by a space in that error message
conflicts with the email signature delimiter.  That's why I've quoted
the lines in the cut-n-paste.

--

73,
Ged.

___

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

[clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate is here!

[Joel Esler (jesler) via clamav-users]

> 
> https://blog.clamav.net/2021/07/clamav-01040-release-candidate-is-here.html 
> 
> 
> ClamAV 0.104.0 Release Candidate is here!
> 
> We are pleased to announce the ClamAV 0.104.0 release candidate 
> .
> 
> 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 
> , or on our Discord 
> , which is bridged with our IRC.
> 
> This release candidate phase is only expected to last about two to four weeks 
> before the 0.104.0 Stable version will be published. Take this opportunity to 
> verify that you 0.104.0 can build and run in your environment. 
> 
>  <>Please submit bug reports to the ClamAV project GitHub Issues 
> .  
> ClamAV 0.104.0 includes the following improvements and changes.
> 
>  
> 
> New Requirements
> 
> As of ClamAV 0.104, CMake is required to build ClamAV.
> 
> We have added comprehensive build instructions for using CMake to the new 
> INSTALL.md file. The online documentation will also be updated to include 
> CMake build instructions.
> The Autotools and the Visual Studio build systems have been removed.
>  
> Major changes
> 
> The built-in LLVM for the bytecode runtime has been removed.
> 
> The bytecode interpreter is the default runtime for bytecode signatures just 
> as it was in ClamAV 0.103.
> We wished to add support for newer versions of LLVM, but ran out of time. If 
> you're building ClamAV from source and you wish to use LLVM instead of the 
> bytecode interpreter, you will need to supply the development libraries for 
> LLVM version 3.6.2. See INSTALL.md to learn more.
> There are now official ClamAV images on Docker Hub.
> 
> Note: Until ClamAV 0.104.0 is released, these images are limited to 
> "unstable" versions, which are updated daily with the latest changes in the 
> default branch on GitHub.
> You can find the images on Docker Hub under clamav 
> .
> 
> Docker Hub ClamAV tags:
> 
> clamav/clamav:: A release preloaded with signature databases.
> 
> Using this container will save the ClamAV project some bandwidth. Use this if 
> you will keep the image around so that you don't download the entire database 
> set every time you start a new container. Updating with FreshClam from the 
> existing databases set does not use much data.
> 
> clamav/clamav:_base: A release with no signature databases.
> 
> Use this container only if you mount a volume in your container under 
> /var/lib/clamav to persist your signature database databases. This method is 
> the best option because it will reduce data costs for ClamAV and for the 
> Docker registry, but it does require advanced familiarity with Linux and 
> Docker.
> 
> Caution: Using this image without mounting an existing database directory 
> will cause FreshClam to download the entire database set each time you start 
> a new container.
> 
> You can use the unstable version (i.e. clamav/clamav:unstable or 
> clamav/clamav:unstable_base) to try the latest from our development branch.
> 
> Please, be kind when using "free" bandwidth for the virus databases and 
> Docker registry. Try not to download the entire database set or the larger 
> ClamAV database images on a regular basis.
> 
> For more details, see the ClamAV Docker documentation 
> .
> 
> Special thanks to Olliver Schinagl for his excellent work creating ClamAV's 
> new Docker files, image database deployment tooling, and user documentation.
> 
> clamd and freshclam are now available as Windows services. To install and run 
> them, use the --install-service option and net start [name] command.
> 
> Special thanks to Gianluigi Tiesi for his original work on this feature.
> 
>  
> 
> Notable changes
> 
> We added these features in 0.103.1 but wanted to re-post them here, as patch 
> versions do not generally introduce new options:
> 
> Added a new scan option to alert on broken media (graphics) file formats. 
> This feature mitigates the risk of malformed media files intended to exploit 
> vulnerabilities in other software. Currently, media validation exists for 
> JPEG, TIFF, PNG, and GIF files. To enable this feature, set AlertBrokenMedia 
> yes in clamd.conf, or use the --alert-broken-media option when using 
> clamscan. These options are disabled by default in this patch, but may be 
> enabled in a subsequent release. Application developers may enable this scan 
> option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for the