Today I installed 0.105.0 to test the new fuzzy image signatures.
I was able to determine the fuzzy hash for a set of given pictures of
questionable content using:
sigtool --fuzzy-img pr0npic.jpg
Alas, I started up my trusty editor an generated an rezeptfrei.hdb
signature file containing:
pr0n1
* Ralf Hildebrandt via clamav-users :
> Today I installed 0.105.0 to test the new fuzzy image signatures.
I'm a moron: "Added image fuzzy hash sub-signatures for logical
signatures" -- thus it must be an LDB file :/
> Alas, I started up my trusty editor an generated an rezeptfrei.hdb
> signature
# dig +short @ns1e.clamav.net. current.cvd.clamav.net. txt
"0.103.6:62:26552:1653485340:1:90:49192:333"
No response from:
# dig +short @ns2a.clamav.net. current.cvd.clamav.net. txt
Out of date:
# dig +short @ns4a.clamav.net. current.cvd.clamav.net. txt
"0.103.6:62:26546:1652981340:1:90:49192:333
We're starting to run clamav on more local hosts and were starting to
see rate limiting messages. So I've setup a local private mirror with
cvdupdate in each of our offices. However now I'm starting to see
warnings like:
Received signal: wake up
ClamAV update process started at Wed May 25 07
Hi there,
On Wed, 25 May 2022, Orion Poplawski via clamav-users wrote:
We're starting to run clamav on more local hosts and were starting to see
rate limiting messages. So I've setup a local private mirror with cvdupdate
... I'm starting to see warnings like:
Received signal: wake up
ClamAV
Almost always once a day, currently between 9:00 and 9:30 am GMT. I scanned
back and the last time there was a twice a day was 23 Dec 2021 and very few no
update days.
-Al-
> On May 25, 2022, at 9:13 AM, G.W. Haywood via clamav-users
> wrote:
>
> Since it's just using DNS requests to check f
