Codesigning with ECC certificate (rather than RSA) - works with SmartScreen?

HI LeonPavesic,

Thank you for your reply. Do you have a source you can name for Microsoft SmartScreen having ECC certificate support? I have been unable to find any references to it online.

I'll highlight the fact that the certificate I'm using is an EV (Extended Validation) code signing certificate. Sellers of EV certs claim that "An EV code signing certificate offers an immediate reputation with Microsoft SmartScreen, so your users will never have to click through a SmartScreen warning in Windows." (https://www.ssl.com/faqs/which-code-signing-certificate-do-i-need-ev-ov/)

Also the Microsoft malware analysts, who have access to the backend systems that track application reputation, are telling me that "the application [REDACTED] has since established reputation and attempting to download or run the application should no longer show any warnings."

So the problem doesn't seem to be on the backend. Which, combined with the anecdotal evidence of other devs with RSA certificates not having this issue, leads me to guess that there may be a problem on the frontend (i.e. locally with SmartScreen on my laptop).

I did find this Microsoft documentation that ECC algorithms are not supported in another area of the Windows Defender infrastructure:

https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/design/select-types-of-rules-to-create#windows-defender-application-control-file-rule-levels

But I am unclear if this would apply directly to Windows Defender Smartscreen.

Thank you,

Leigh