On 15.09.20 14:24, Gary R. Schmidt wrote:
> Well, that was entertaining.
less of an adventure here (CentOS 7), but my spec file that has been
working without modifications since clamav 0.9x needed some patching
today, or else clamav-milter refused installation with:
Error: Package: clamav-milte
You may want to subscribe to the mailing list
clamav-viru...@lists.clamav.net
for a changelog of the virus db. Indeed this list only sends one mail
per day.
On 29.07.20 01:01, Paul Kosinski via clamav-users wrote:
> "...we also only release updates once a day."
>
> Are there *never* any urgent v
Thank you Micah
In that case I'll just lean back and wait for the bugfix release :-)
On 02.10.19 22:52, Micah Snyder (micasnyd) wrote:
> Hi lukn,
>
> You're not missing something. It appears that configure changes between
> ClamAV 0.102.0-rc and 0.102.0 broke bui
.5 20150623 (Red Hat 4.8.5-36)
but in such cases I'd expect a loud error message, compile abort yada
yada - not awkward output silence.
Any ideas? Any additional information needed?
Best regards
lukn
___
clamav-users mailing list
clamav-use
those old boxes, gotta replace them anyway
eventually...
thx
lukn
On 16.11.18 20:45, Micah Snyder (micasnyd) wrote:
> That is... bizarre. What does your clamd configuration look like?
> Specifically, do you have `ScanOnAccess` enabled and set to watch specific
> mount or directory p
ure --prefix=%{_prefix} --enable-milter
make check
make
The issue only occured recently... maybe some borked signature?
Any ideas?
regards
lukn
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clam
Hi
cudasvc was recently listed on Spamhaus' DBL. Looks like Barracuda has
some kind of issues with their service.
The other question is, why do people use such link cloakers?
On 27.08.2018 22:44, Mark G Thomas wrote:
> Hi,
>
> But, there are more. This is nuts.
>
> # sigtool --find-sigs MB
ver, before this rule gets rectified officially).
>
>
>
> On 14 August 2018 22:40:49 BST, lukn wrote:
>> Same here. I agree this rule is causing too many FPs to remain active.
>> Therefore I ended up whitelisting this rule.
>>
>>
>>> I now
Hi
You cannot whitelist a sender in ClamAV. Whitelisting happens in the
software that calls ClamAV.
The alternative is to disable spoofing checks in ClamAV configuration.
They're not enabled by default, so if your ClamAV checks spoofing, then
someone enabled it on purpose.
As Al already pointed
Same here. I agree this rule is causing too many FPs to remain active.
Therefore I ended up whitelisting this rule.
> I now only run in report mode and not delete mode
I don't understand the whish to leave the decision of data destruction
to a third party software. My system should follow my rul
On 02.03.2018 15:12, Micah Snyder (micasnyd) wrote:
> The ClamAV version check should be updated now. My apologies for the
> inconvenience.
Also confirming that the issue has been resolved. Thanks for handling it
and thanks for the new version of ClamAV!
_
On 02.03.2018 09:21, Al Varnell wrote:
> They just need to update DNS with updated version when they come in. Not a
> big deal. It only results in display of the warning. Should not impact
> operations in any way.
this is correct, 0.99.4 is fully operational and getting signature
updates. But t
same here. #fail :-P
I guess we'll have to live with that until Talos people go back to
office. Reminds me a bit of that broken signature recently... push stuff
Thursday evening, then go home.
Maybe the releases need a better timing. Like in the morning hours of
Talos Office Time, to allow ample
As ClamAV/Thalos is owned by Cisco I assume all ClamAV employees are
located in Silicon Valley area and therefore still enjoying a good
Californian night's sleep.
On 26.01.2018 13:17, maxal wrote:
> nobody of clamav/cisco reading this list? as the impact is heavy and
> probably worldwide - anyone
stop freshclam daemon
On 26.01.2018 11:54, Rajesh M wrote:
> hi all
>
> even though i removed
>
> daily.cld
> main.cld
> bytecode.cld
> mirrors.dat
>
> all of these has been recreated automatically
>
> i am not running freshclam via a cron job
>
> help required in disabling clam updates
>
aming failed
clamd[11895]: accept() failed:
I suspect a toxic signature keeps killing clamd
On 26.01.2018 07:47, lukn wrote:
> Good morning list
>
> same here, since about 4am CET we see permanent crashes of clamd.
> Process indeed disappears, but logging is minimal. All I see is:
Good morning list
same here, since about 4am CET we see permanent crashes of clamd.
Process indeed disappears, but logging is minimal. All I see is:
clamd[25989]: instream(127.0.0.1@58142): Can't open file or directory ERROR
clamd[25989]: accept() failed:
the second line repeats several dozen ti
Hello List and Joel
I still see freshclam failures for mirror 193.230.240.8
WARNING: getfile: daily-23823.cdiff not found on database.clamav.net
(IP: 193.230.240.8)
WARNING: getpatch: Can't download daily-23823.cdiff from database.clamav.net
freshclam --list-mirrors
[..]
Mirror #2
IP: 193.230.2
Hello List
Same here, I do see FPs with
BC.Win.Exploit.CVE_2017_11244-6335828-0
hitting legitimate corporate files (so no submission possible from me
either).
md5sum of the affected file is
bf20323e1cea2c2c3fc26d09956dd906
(don't know if this is helpful without the actual file...)
On 13.09.2017
Hello Tomasz
Am 29.04.2011 16:45, schrieb Tomasz Kojm:
Please open a bug report at bugs.clamav.net and attach the HTML file if
possible.
Thanks for your quick reply, bug has been filed:
https://wwws.clamav.net/bugzilla/show_bug.cgi?id=2764
bye
lukn
ommended way of creating md5 signatures from HTML-files?
My current version of clamav is 0.97 from Debian repositories:
clamscan --version
ClamAV 0.97/13022/Fri Apr 29 08:03:10 2011
thanks and have a good weekend!
lukn
___
Help us build a comprehensive
21 matches
Mail list logo
