Skip to content

docs(readme): distinguish signed release binaries from unsigned source builds in SmartScreen section #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MukundaKatta wants to merge 1 commit into from
Closed

docs(readme): distinguish signed release binaries from unsigned source builds in SmartScreen section #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,14 @@ make build

### Windows SmartScreen

The Windows binary is unsigned. On first run SmartScreen may block it with
"Windows protected your PC". Click **More info → Run anyway**. To avoid the
prompt altogether, unblock the executable before running:
Release binaries are Authenticode-signed with Azure Trusted Signing (see the
`sign-windows` job in `.github/workflows/release.yml`), so SmartScreen should
not prompt for official downloads from GitHub Releases.

If you build from source (`go install` / `make build`), the resulting
`ana.exe` is **not** signed and SmartScreen may still block it on first run
with "Windows protected your PC". Click **More info → Run anyway**, or
unblock the file before running:

```powershell
Unblock-File -Path .\ana.exe
Expand Down