I would 100% expect that that a certificate issue would lead to a priority out
of schedule release, in this case a 4.26.1 or 4.26.0.1 as the case may be, its
actually a major issue when security mechanisms are flagging a legit publication
as not legit, you do NOT want users making security exceptions for your
software. -- Darren Duncan
On 2020-09-18 4:59 p.m., richard coleman wrote:
> Dave,
>
> Thanks for the update. Are you going to rerelease the update with a valid
> certificate, or at least publish the SHA256 hash for the file so that we can
> verify that it downloaded correctly?
>
> Thanks again,
>
> rik.