I received a response from Vipre a short time ago stating that they
have fixed this FP. A test with the current def confirms that.
--
Brian
___
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-u
On 18 Feb 2020 at 15:16, Steve Basford wrote:
>
> Other AV's are also flagging... but maybe the same FP signature:
>
> https://www.virustotal.com/gui/file/8244bc93e71a78be156adf1bfef0785b4f3cd6725d095ffe7ed528ff08e8458c/detection
This report is very different from the one produced yesterday
morni
File libclamunrar.dll from ClamAV 0.102.2 win x86 portable is being
quarantined by Sunbelt Vipre Enterprise as Trojan.GenericKD.42582612.
The first detection was at 5:44 PM EST on Friday Feb 14.
Microsoft is the only product that flags it as infected on VirusTotal
as Trojan:Win32/Detplock.
I sub
The error pointed me to a typo in clamd.conf. Problem solved.
Thank you Micah.
--
Brian Fluet
On 16 Oct 2019 at 14:09, Micah Snyder (micasnyd) wrote:
> Hi Brian,
>
> Try running clamd.exe from cmd.exe so you can see what the error
> message is. It could be that clamd.conf.
otten to rem-out the .conf "Example" line but I hadn't. I have
checked the paths in the .conf (log,temp,database) and that another
instance of clamd was not running. How else do I troubleshoot?
FWIW, v0.101.4 is working fine.
--
Brian Fluet
___
y whether associated with updating databases or more along
the lines of integrity checks.
"Perform a database check" in clamd.conf
"Number of database checks per day" in freshclam.conf
Brian Fluet
___
clamav-users mai
t is controlling the freshclam frequency. I
will look into that.
Brian Fluet
___
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
ault of 12.
In clamd.conf I have set the "Perform a database check" to 3600 which
should be hourly (right?) although I don't know whether this has
anything to do with freshclam frequency.
Advice would be appreciated.
TIA
Brian Fluet
___
cl
inutes. I suppose the .cvd could be a few hours old by the
> time it gets posted, so doesn't seem like there's any reason to be
> concerned.
>
> -Al-
>
> On Aug 6, 2019, at 07:42, Brian Fluet via clamav-users
> wrote:
>
> I upgraded to v0.10
I upgraded to v0.101.3 yesterday afternoon. This morning I notice
the daily.cld is over 28 hrs old. The freshclam log reports that
it's up to date but it's age has me curious about that age at which
to become concerned.
Also, after upgrading to v0.101.3 I'm seeing these entries in the
freshc
Here's the log content of the most recent freshclam download:
--
ClamAV update process started at Fri Dec 7 13:59:41 2018
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60,
builder: sigmgr)
Downloading daily-25186.cdiff [100%]
daily.cld updated (
Hi All,
Since installing Win32 portable v0.101.0 I am seeing the following
entry in the fresclam.log at each download:
Can't query daily.25186.101.1.1.6810BD8A.ping.clamav.net
Is this of concern?
--
Brian
___
clamav-users mailing list
clamav-user
Thank you Micah. I'll uninstall and then start using the portable
version files.
This won't be a problem. I used extracted files from the .msi for
years only recently doing an actual install (don't remember why
though).
Brian
___
clamav-users mai
Will the new .exe installer automatically update a ClamAV for Win32
that is installed in a non-standard location (not in \Program files)?
Brian
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinf
Thanks for the url to the release notes.
I'm using the Win32 package from clamav.net in conjunction with
Mercury Mail Transport System which passes messages to clamd.
--
Brian Fluet
___
clamav-users mailing list
clamav-users@lists.clamav.net
I use ClamAV for Win32 and am wondering if there is a way to tell
when an update contains a change to either of the .conf files so as
to know when it's ok to stay with the existing ones.
Thanks.
Brian Fluet
___
clamav-users mailing list
c
tup.exe in the hopes of
extraction but no joy. I understand that I'm probably the only
updating in this manner but would be grateful to have access to the
runtime library files if possible.
BTW, the windows specific changes to the conf files were noticed and
are very much appreciated!
Background: Using ClamAV for Win32. My usage has allowed me to use
it without ever having to install it. Instead I simply extracted the
.msi. Updates were done by replacing previous files with new ones.
The directory structure of the extracted .msi from the
clamav-0.100.0-win-x86.zip file i
curiosity I retrieved the version info for clamd...
Clamd v0.99.4:
c:\clamav\clamd --version
ClamAV clamav-0.99.4/24377/Fri Mar 09 04:13:20 2018
Clamd v0.99.3:
c:\clamav_0_99_3\clamd --version
ClamAV devel-clamav-0.99.2-20-g224f73461/24377/Fri Mar 09 04:13:20 2018
--
Brian Fluet
I'll take the blame for the flame. I registered on the list in haste in order
to add my
experience to the discussion about the warning message that I was then reading
on the
archive web page, in threaded view. I my mind, my post would pick up that
thread. I
completely forgot about the nat
d have taken time to mention the exact message
> unasked in his original post - i love people starting with "I just
> subscribed to the list in the hopes of understanding the issue with
> the warning being logged by freshclam"
>
> On Mar 7, 2018 9:33 AM, "Reindl Harald&quo
I've been to http://www.clamav.net/documents/upgrading-clamav
I didn't find anything that provided me with a clue that would
explain why or how to fix the warning that indicates an outdated
version while at the same time reporting a local version of
clamav-0.99.4 (current version, correct?).
__
Here's the most recent freshclam log entry:
Wed Mar 07 12:19:08 2018 -> ClamAV update process started at Wed Mar 07
12:19:08 2018
Wed Mar 07 12:19:08 2018 -> WARNING: Your ClamAV installation is OUTDATED!
Wed Mar 07 12:19:08 2018 -> WARNING: Local version: clamav-0.99.4 Recommended
version: 0.99
I just subscribed to the list in the hopes of understanding the issue with the
warning being
logged by freshclam. The discussion indicates that the issue is resolved but
the warning is
still being logged here. Is there something I need to do on this end?
__
24 matches
Mail list logo