El vie., 20 may. 2022 14:50, Roger Marquis escribió:
> Thank you Florian! If there are any policy changes that can be made to
> prevent this sort of issue (critical vulnerabilities not getting patches
> or not showing up in vuln.xml for days or weeks after a CVE and/or
> update) please do recomm
Thank you Florian! If there are any policy changes that can be made to
prevent this sort of issue (critical vulnerabilities not getting patches
or not showing up in vuln.xml for days or weeks after a CVE and/or
update) please do recommend them to, well, who does set ports/security
management poli
On 19.05.22 09:30, Andrea Venturoli wrote:
Hello.
I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
latter two closing "several CVE fixes".
However, the port was not updated and not even portaudit entries were
added.
Was this overlooked?
Are the FreeBSD ports somehow
On 5/19/22 09:38, Kurt Jaeger wrote:
There's a PR waiting:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263944
Sorry, I missed that.
Hi!
> I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
> latter two closing "several CVE fixes".
>
> However, the port was not updated and not even portaudit entries were added.
>
> Was this overlooked?
There's a PR waiting:
https://bugs.freebsd.org/bugzilla/show_bug.cgi
Hello.
I see Clamav 0.105.0, 0.104.3 and 0.103.6 were released on May 5th, the
latter two closing "several CVE fixes".
However, the port was not updated and not even portaudit entries were added.
Was this overlooked?
Are the FreeBSD ports somehow not affected?
Thanks in advance.
bye
