Windows SmartScreen flags recent releases as suspect despite signing #120326

New Issue

@ThomasDinges just prodding you as release manager, as i have no influence over this, if you want to pass the problem to someone better equipped to deal with it, feel free to do so.

We got the new cert in september 2023, we should have rebuild the reputation by now, i don't think this codesign cert is working super well for us, the only difference i see is the previous codesign cert was RSA based while the current one is ECC based. How smartscreen works internally is a bit of a mystery but it sure doesn't seem to like our current cert.

unsure where to go with this, can you prod around HQ a bit? maybe contact our cert vendor? see if they have seen this before?

@ThomasDinges just prodding you as release manager, as i have no influence over this, if you want to pass the problem to someone better equipped to deal with it, feel free to do so. We got the new cert in september 2023, we should have rebuild the reputation by now, i don't think this codesign cert is working super well for us, the only difference i see is the previous codesign cert was RSA based while the current one is ECC based. How smartscreen works internally is a bit of a mystery but it sure doesn't seem to like our current cert. unsure where to go with this, can you prod around HQ a bit? maybe contact our cert vendor? see if they have seen this before?

Harley Acheson commented

2024-04-05 22:07:24 +02:00

The clue here is "unrecognized app" and this has to do with code-signing and nothing to do with the code inside.

Blender signs these builds with an ECC certificate (rather than RSA) which can cause these issues with SmartScreen. As far as I know this has been a problem for a long time with daily builds, but not with official releases.

But when presented with this screen, if you know you have downloaded it from a trusted location (like Blender.org), you can click "More Info", then press "Run Anyway"

The clue here is "unrecognized app" and this has to do with **code-signing** and nothing to do with the code inside. Blender signs these builds with an ECC certificate (rather than RSA) which can cause these issues with SmartScreen. As far as I know this has been a problem for a long time with daily builds, but not with official releases. But when presented with this screen, if you know you have downloaded it from a trusted location (like Blender.org), you can click "More Info", then press "Run Anyway"

Jesse Yurkovich changed title from ~~Windows consider blender 4.2 as thread~~ to Windows SmartScreen flags recent releases as suspect despite signing

2024-04-05 22:44:26 +02:00

CODACOD commented

2024-04-05 23:33:30 +02:00

The clue here is "unrecognized app" and this has to do with code-signing and nothing to do with the code inside.

Blender signs these builds with an ECC certificate (rather than RSA) which can cause these issues with SmartScreen. As far as I know this has been a problem for a long time with daily builds, but not with official releases.

But when presented with this screen, if you know you have downloaded it from a trusted location (like Blender.org), you can click "More Info", then press "Run Anyway"

yes this happen only in daily build .
i did downloaded this from blender.org/download/daily/ .

> The clue here is "unrecognized app" and this has to do with **code-signing** and nothing to do with the code inside. > > Blender signs these builds with an ECC certificate (rather than RSA) which can cause these issues with SmartScreen. As far as I know this has been a problem for a long time with daily builds, but not with official releases. > > But when presented with this screen, if you know you have downloaded it from a trusted location (like Blender.org), you can click "More Info", then press "Run Anyway" yes this happen only in daily build . i did downloaded this from blender.org/download/daily/ .

Pratik Borhade added

Module

Platforms, Builds & Tests

and removed

labels 2024-04-06 08:03:45 +02:00

Thomas Dinges commented