Windows signing #384
Labels
dif/expert
Extensive knowledge (implications, ramifications) required
effort/days
Estimated to take multiple days, but less than a week
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
P3
Low: Not priority right now
status/ready
Ready to be worked
Problem
Lack of signing on Windows means that when a binary is run for the first time and tries to access networking it gets Windows Defender Firewall warning with "Publisher: Unknown":
My guess is that over time, MS Windows will get more and more strict, just like macOS did in recent years.
Solution: sign windows binaries
sign-windows
job aftersign-macos
(sequentially) should be easy and fast enough(we can parallelize them if needed, but given how long macos signing takes, the difference will be minimal)
The text was updated successfully, but these errors were encountered: