I have never had a Windows app certified, but I don't think there is any
cost associated with it, it's just a process at Microsoft. This sort of
signing in not a TLS certificate possibly involving cost (though most
people use Let's Encrypt now).
This is a page from Microsoft. I think it's outdated but the principles
would remain roughly the same.
https://learn.microsoft.com/en-us/windows/win32/win_cert/windows-certification-portal
If there is any interest I'd be happy to investigate this more
seriously. perhaps this should be on the devel list?
Andrew
On 16/11/2022 7:55 am, Karlin Hiegh wrote:
On 11/15/2022 2:30 PM, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
b) whether we would need to buy a certificate for that.
I think the answer is "yes, need to buy certificate."
And even that is no guarantee of executables not getting flagged after
downloads, UNLESS there is a large and powerful outfit behind the
signature that the security companies wish to avoid angering.
<http://blog.nirsoft.net/2009/05/17/antivirus-companies-cause-a-big-headache-to-small-developers/>
If a certificate WAS pursed, with macOS having the greatest need I
expect, it looks like it would need contact info and a mailing
address. That is where I stopped research, having no idea what would
be used there.
