178 ms·
The post has now been removed from the web site. Archive.org has a copy: https://web.archive.org/web/20200826113615/https://www.rarlab.com/revoked591.html https
by tgsovlerkhgsel 6y ago
The post has now been removed from the web site. Archive.org has a copy: https://web.archive.org/web/20200826113615/https://www.rarlab.com/revoked591.html https://web.archive.org/web/20200826113615/https://www.rarla...
Unfortunately, I can't find any update/conclusion.
However, I did find https://sectigo.com/resource-library/the-what-when-and-why-of-revoking-certificate-signed-malware https://sectigo.com/resource-library/the-what-when-and-why-o..., where Sectigo (the CA that presumably revoked the certificate, formerly also known as Comodo) mentions a previous incident, confirms that they didn't notify the certificate owner in that incident, and promises to "review" their practices. Given that RARLAB wrote "We had not received any notification, neither before nor after the revocation", I suspect Sectigo didn't improve.