Digitally sign produced binaries? (VS Extension) #427
Replies: 3 comments 2 replies
-
I don't believe there's any plan to do this, but if it's something that's valuable we can look into it. I can foresee the only real questions are going to be around the burden of certificate management. |
Beta Was this translation helpful? Give feedback.
-
Thanks for bringing up this topic. I'm also not an expert of this, but when I did a research earlier for a work project I found that there are two kind of certificates that could be potentially used for such thing (see here for details):
None of them are for free and but the EV certificates are significantly more expensive. So my first question would be whether a signature with an OV certificate would be enough for getting into the white list or automatic white listing works only with EV certificates? (E.g. to avoid untrusted warning for Windows installers, you need an EV certificate.) |
Beta Was this translation helpful? Give feedback.
-
SignPath could be an option: https://signpath.org/ |
Beta Was this translation helpful? Give feedback.
-
Some organizations use AppLocker to block untrusted binaries, and the Reqnroll VS Extension is one such binary that get's blocked as it is invoked by VS, and thus intellisense for Reqnroll is not working.
The best (most secure) way to white list a binary is to trust the Digital Signature of a binary.
A work around is to white list a directory but that is not the prefered way to do it and should be avoided if possible.
Are there any plans of digitally signing the produced binaries? (Not to be confused with Strong Naming)
Beta Was this translation helpful? Give feedback.
All reactions