Swift release on Windows blocked by Windows Defender about swift-build HOT 3 CLOSED

What do you mean by official certificate? If you mean a non-self-signed one, that is something which requires a purchased certificate which no one has volunteered to cover the costs for. As such there is no way to get the certificate cross signed by a trusted root authority.

from swift-build.

What do you mean by official certificate? If you mean a non-self-signed one, that is something which requires a purchased certificate which no one has volunteered to cover the costs for. As such there is no way to get the certificate cross signed by a trusted root authority.

Even if you sign it, it is not guaranteed that I won't see this message from MS, except by using an etended validation code signing certificated. You could also submit your app for malware analysis to Microsoft.
I am surprised that this exe is blocked by Defender, I think it's the firts time it happens.

https://stackoverflow.com/questions/48946680/how-to-avoid-the-windows-defender-smartscreen-prevented-an-unrecognized-app-fro/66582477#66582477

I will not install an exe blocked by Windows Defender so I will not test swift on Windows

from swift-build.

I don't think that the submitting the binary to Microsoft works, as we churn through them pretty rapidly (these are nightly snapshots after all). The EV certificate is the solution, but that is not exactly cheap, so that is currently not viable ATM. It is unfortunate that it will prevent you from using it. The alternative is that you can down the binaries directly from Azure if you like (the signature is the same) - but you know that the binaries that are being packaged are the ones built there.

from swift-build.