Re: [clamav-users] Long Term Support (LTS) program proposal

[Matus UHLAR - fantomas]

On 30.07.21 14:38, Paul Kosinski via clamav-users wrote:

Recently, the bandwidth hogging episodes have resulted in rapid changes to
ClamAV versions, followed by EOL of versions that many people (not
including me) were still using.  So recently I have had to spend far more
time on updating ClamAV than updating anything else I use.  And since I
can't count on Debian (or even update-happy OpenSUSE) keeping up with
these (now rapid) changes, I have always built ClamAV from source, ever
since I started using it 16+ years ago.


can't count on Debian?

i think clamav and spamassassin were the main reasons the volatile (now
updates) archive was created and maintainers are trying to get active clamav
into debian.

Yes, LTS debian has 0.102.4 and not 0.103, but it still works, doesn't it?

--
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.
A day without sunshine is like, night.

___

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] Opinion wanted: Change default config directory usr/clamav

[Avram-Teodor Berindeie]

Ever since I started using Linux (RedHat before becoming a commercial
distribution and then Slackware for a total of about 20 years) I have
always installed the antivirus, including ClamAV in /opt with .
Configuration files have always been in /opt/clamav/etc
Now they will be in /opt/clamav/etc/clamav whatever ...
I will manage to modify the startup scripts (not systemd, it doesn't exist
in Slackware) but from my point of view it doesn't help me at all!

___

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] Opinion wanted: Change default config directory usr/clamav

[G.W. Haywood via clamav-users]

Hi there,

On Sat, 31 Jul 2021, Micah Snyder (micasnyd) via clamav-users wrote:


... change the default directory for the config files from
/etc to /etc/clamav. ...


This is relatively unimportant.

If it were up to me, I'd look to see if there's already what seems to
be an existing, sane, config directory and, if found, use it.  Perhaps
confirm it with the user building it first; you could even ask for it.
If not found, by all means create something in /usr/local/etc/opt/ or
whatever floats your FHS-compliant boat at the time.  But please try
not to mess things up for existing users who've had to put up with
quite enough of this kind of thing from package mantainers already.


Unfortunately, I procrastinated it so hard I forgot to merge it
before the first release candidate. ... I would like your opinion.


This is very important.  Think in terms of, say, trashing the database
for half a million customers.

I've already mentioned privately to Joel that I'm concerned about the
quality control over there.  This reinforces the feeling.  This is the
kind of thing which could de-orbit the ISS and cannot be excused.

Most people think quality control means testing.  It doesn't.

It's mostly about how you design, and document, and implement all your
procedures and processes so that things can *never* get forgotten, or
left out, or put in, by accident.  You need to get a very firm grip on
those things now, before you do more or less anything else.  It's the
manufacturing equivalent of growing up.

There must be somebody in the Cisco empire who deals with this stuff.
Find him, and spend some quality time with him[*].  It'll be worth it.

--

73,
Ged.
[*] The masculine embraces the feminine where the context permits.

___

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] Long Term Support (LTS) program proposal

[Paul Kosinski via clamav-users]

On Sat, 31 Jul 2021 02:37:53 +
"Joel Esler (jesler)"  wrote:

> > On Jul 30, 2021, at 14:41, Paul Kosinski via clamav-users 
> >  wrote:
> > 
> > (I don't see exactly how a LTS would have helped with the bandwidth issue, 
> > but I suppose it wouldn't have made it any more disruptive.)  
> 
> 103.2 and 103.3 are much more respectful to bandwidth than any past version.  
> We’ve been working with Cloudflare on the development of a feature that is 
> exactly optimized to handle these changes, and they are almost ready to 
> deploy it.  We’ve tested it out and it works well, so we’re just waiting on a 
> few more updates. 
> 


What I meant was that if (e.g.) 0.103.1 had been LTS, that alone wouldn't have 
solved the bandwidth overload. Making (e.g.) 0.104.x LTS will (of course) 
mitigate future bandwidth problems.

___

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] Opinion wanted: Change default config directory usr/clamav

[Paul Kosinski via clamav-users]

On Sat, 31 Jul 2021 12:03:36 +
"Micah Snyder \(micasnyd\) via clamav-users"  
wrote:

> Hi all,
> 
> I could use your opinion about a change we'd planned to make in 0.104. By 
> request, I'd made this pull request to change the default directory for the 
> config files from /etc to /etc/clamav. The purpose being to 
> de-clutter /usr/local/etc: https://github.com/Cisco-Talos/clamav/pull/182
> 
> I procrastinated merging it for a long time because while it feels like a 
> good change it will require a change to our test framework and would likely 
> break scripts for other users as well. Some justification for the change at 
> this time is that with the build system change to cmake, users will likely 
> have to change the same scripts anyhow so we don't have any better time.
> 
> Unfortunately, I procrastinated it so hard I forgot to merge it before the 
> first release candidate. Now, I can't decide if it's right to merge it before 
> the second release candidate or throw it away. I would like your opinion.
> 
> Regards,
> Micah


When are started using ClamAV (<= 0.88.4), I built it in "/opt". Since then, 
it's always in "/opt/clamav.d/clamav.0.major.minor" with a symbolic link like 
"/opt/clamav -> /opt/clamav.d/clamav.0.103.3". This allows me to keep previous 
versions easily accessible in case of a problem.

The only real problem I remember having was when the latest version of 
libclamav wasn't compatible with the current version of HAVP (which I also 
build from source into "/opt" in the same manner). Fortunately, HAVP was 
updated soon after, but it allowed me to scan email with the latest ClamAV 
while keeping HAVP working adequately.

P.S. I tend to think "/opt" is preferable to "/usr" for software like ClamAV, 
at least until Linux distributors keep them up to date more diligently (as 
befits security software), so users don't have to build them on their own,

___

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] Opinion wanted: Change default config directory usr/clamav

[Mark Fortescue via clamav-users]

Hi Micah,

On my uBuntu distributions the config files have been in /etc/clamav at 
least since uBuntu 10.04 LTS so I see no issue with the change.


It makes /usr/local/etc consistent with /etc which is always a good 
thing when you are trying to debug/find/compare things when something 
has gone wrong.


Regards
Mark.

On 31/07/2021 13:03, Micah Snyder (micasnyd) via clamav-users wrote:

Hi all,

I could use your opinion about a change we'd planned to make in 0.104. 
By request, I'd made this pull request to change the default directory 
for the config files from /etc to /etc/clamav. The 
purpose being to de-clutter /usr/local/etc: 
https://github.com/Cisco-Talos/clamav/pull/182


I procrastinated merging it for a long time because while it feels like 
a good change it will require a change to our test framework and would 
likely break scripts for other users as well. Some justification for the 
change at this time is that with the build system change to cmake, users 
will likely have to change the same scripts anyhow so we don't have any 
better time.


Unfortunately, I procrastinated it so hard I forgot to merge it before 
the first release candidate. Now, I can't decide if it's right to merge 
it before the second release candidate or throw it away. I would like 
your opinion.


Regards,
Micah


___

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] Opinion wanted: Change default config directory usr/clamav

[Michael Orlitzky via clamav-users]

On Sat, 2021-07-31 at 14:47 +0200, Arjen de Korte via clamav-users
wrote:
> 
> What might be useful to add, is an option to set the name of the UNIX  
> socket (which is hard coded now) through a cmake option. In openSUSE  
> we patch this to a different name, but this needs to be done in  
> several files, so a cmake option would help.
> 

If the configuration files are changed to templates, the line

  #LocalSocket /tmp/clamd.socket

(which creates a security vulnerability) could become

  #LocalSocket @RUNSTATEDIR@/clamav/clamd.ctl

instead. That's not _completely_ configurable, but it's a secure
setting that could be used by everyone without patching.



___

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] Opinion wanted: Change default config directory usr/clamav

[Arjen de Korte via clamav-users]

Citeren "Micah Snyder (micasnyd) via clamav-users"  
:



Hi all,

I could use your opinion about a change we'd planned to make in  
0.104. By request, I'd made this pull request to change the default  
directory for the config files from /etc to  
/etc/clamav. The purpose being to de-clutter /usr/local/etc:  
https://github.com/Cisco-Talos/clamav/pull/182


I procrastinated merging it for a long time because while it feels  
like a good change it will require a change to our test framework  
and would likely break scripts for other users as well. Some  
justification for the change at this time is that with the build  
system change to cmake, users will likely have to change the same  
scripts anyhow so we don't have any better time.


Unfortunately, I procrastinated it so hard I forgot to merge it  
before the first release candidate. Now, I can't decide if it's  
right to merge it before the second release candidate or throw it  
away. I would like your opinion.


Either way is probably fine, there is always the APP_CONFIG_DIRECTORY  
option to change the location. As long as this is honored, just  
mentioning the change in the changelog should be enough.


What might be useful to add, is an option to set the name of the UNIX  
socket (which is hard coded now) through a cmake option. In openSUSE  
we patch this to a different name, but this needs to be done in  
several files, so a cmake option would help.






___

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] Opinion wanted: Change default config directory usr/clamav

[Frans de Boer]

On 7/31/21 2:03 PM, Micah Snyder (micasnyd) via clamav-users wrote:

Hi all,

I could use your opinion about a change we'd planned to make in 0.104. 
By request, I'd made this pull request to change the default directory 
for the config files from /etc to /etc/clamav. The 
purpose being to de-clutter /usr/local/etc: 
https://github.com/Cisco-Talos/clamav/pull/182 



I procrastinated merging it for a long time because while it feels 
like a good change it will require a change to our test framework and 
would likely break scripts for other users as well. Some justification 
for the change at this time is that with the build system change to 
cmake, users will likely have to change the same scripts anyhow so we 
don't have any better time.


Unfortunately, I procrastinated it so hard I forgot to merge it before 
the first release candidate. Now, I can't decide if it's right to 
merge it before the second release candidate or throw it away. I would 
like your opinion.


Regards,
Micah
In the past I already used /etc/clamav for the configuration file, just 
for the same reason: avoiding cluttering.
Now, since /etc has become the norm, it's only logical - for the 
same reason - to use the proposed form of /etc/clamav as the 
default. I already use it this way.


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] Opinion wanted: Change default config directory usr/clamav

[Micah Snyder (micasnyd) via clamav-users]

Hi all,

I could use your opinion about a change we'd planned to make in 0.104. By 
request, I'd made this pull request to change the default directory for the 
config files from /etc to /etc/clamav. The purpose being to 
de-clutter /usr/local/etc: https://github.com/Cisco-Talos/clamav/pull/182

I procrastinated merging it for a long time because while it feels like a good 
change it will require a change to our test framework and would likely break 
scripts for other users as well. Some justification for the change at this time 
is that with the build system change to cmake, users will likely have to change 
the same scripts anyhow so we don't have any better time.

Unfortunately, I procrastinated it so hard I forgot to merge it before the 
first release candidate. Now, I can't decide if it's right to merge it before 
the second release candidate or throw it away. I would like your opinion.

Regards,
Micah

___

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