[bisq-network/bisq] Add command for signing windows executables with the default code signing certificate (#3772)

[Devin Bileck]

Posting my results here.

I still get the smartscreen dialog, although it does show you as the publisher:
![image](https://user-images.githubusercontent.com/603793/70599952-551ffb80-1ba3-11ea-86de-4e9ae8f0438c.png)

As mentioned [here](https://blogs.msdn.microsoft.com/vsnetsetup/2013/01/09/windows-smartscreen-prevented-an-unrecognized-app-from-running-running-this-app-might-put-your-pc-at-risk):

> the SmartScreen will continue to warn about the application until the certificate develops a reputation. But it would display a valid publisher name instead of unknown publisher.

> Although not required, programs signed by an EV code signing certificate* can immediately establish reputation with SmartScreen reputation services even if no prior reputation exists for that file or publisher. EV code signing certificates also have a unique identifier which makes it easier to maintain reputation across certificate renewals.

I am not sure if the EV certificate is worth the hassle, nor am I sure how long it would take to develop reputation with the standard certificate.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3772#issuecomment-564416620
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191210/a04d4396/attachment.html>