Recently after replacing our code signing certificate, we notified that the Avast antivirus blocks our applications with the new certificate, though last week several files were whitelisted for us by Avast, newly signed files are still being flagged by Avast. Please, add our certificate to the whitelist, this is required, because our files are often updated and resigned, unfortunately, every time the antivirus blocks them. This issue prevents our users from running the game from our services. Please, resolve this issue.
If you have any questions or need more information, feel free to contact me.
It’s an old thread, but I’ve got the same problem with new certificate. What is the proper format I should send the new certificate? CER, CRT? Base64 or DER? I’ve uploaded base64 CER to the whitelisting program FTP some time ago, but sth is wrong, the exe files signed by new certificate are not whitelisted.
The certificate is not whitelisted per se (i.e. there’s no point in uploading the cert itself), only based on actual samples (i.e. upload e.g. a few executables signed by that new cert).
