Signed binary

Signing the binary will prevent Windows to display the warning message from Microsoft SmartScreen saying this software is unknown and may not be safe.

A code signing certificate is not free. It's really expensive (like several hundreds euros a year). Certum is the cheapest Certification Authority (CA) I found for an open-source project. [It's 25€/year](https://shop.certum.eu/open-source-code-signing-code.html) (30€/year with taxes because I'm French) but it won't even remove the SmartScreen warning.

I'd need to pay 250$ minimum **per year** to remove the warning. It is way too much and I don't want to collect donation for this. This is really a racket.

[More info on the reputation system of Microsoft SmartScreen](https://stackoverflow.com/questions/48946680/how-to-avoid-the-windows-defender-smartscreen-prevented-an-unrecognized-app-fro/66582477#66582477)

The thing is there is now a completely new FOSS Signing Service called [sigstore](https://www.sigstore.dev/) which looks amazing but it won't solve the SmartScreen warning issue.

The issue is about signing the binary for Windows to avoid SmartScreen warnings. Research sigstore for FOSS signing and understand Windows code signing requirements. Look at the build process for the Rust GUI to see where the binary is produced. Determine if a certificate is needed and how to integrate signing into the release workflow.

Written by the indexing model from the issue text.