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!
_
Confirm.
It's ok right now.
02.03.2018 20:12, Micah Snyder (micasnyd) пишет:
> The ClamAV version check should be updated now. My apologies for the
> inconvenience.
>
> I put in the ticket to do the update yesterday as soon as the release went
> out. However, our operations staff had an unre
The ClamAV version check should be updated now. My apologies for the
inconvenience.
I put in the ticket to do the update yesterday as soon as the release went out.
However, our operations staff had an unrelated critical issue they were
actively working on, so I gave them the go-ahead to updat
Understood.
Sent from my iPhone
> On Mar 2, 2018, at 03:28, lukn wrote:
>
>> 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 w
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
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.
-Al-
On Fri, Mar 02, 2018 at 12:01 AM, lukn wrote:
> same here. #fail :-P
>
> I guess we'll have to live with that until Talo
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