Need Better Overview for Code Signing Certificates
walrus_coder said 1 year ago:
I am not finding any actually useful information here about how/why/where one handles code signing files and what process to use in installing them. More specifically, an explanation of what gets purchased, who handles which parts of it (e.g. who ends up with what data to provide what service such as a certifying authority), how the stuff that is downloaded to a dev. machine is explicitly delivered, why must it be transformed, where must it be put, how it gets inside something to actually sign an application, etc. etc. etc. All I am finding is use this tool that microsoft says not to use anymore and other random bits of unrelated factoids that don’t add up to a step by step process with an explanation alongside it.
So: what is desired is…
An explanation of what EXACTLY you will get from GoDaddy if you buy a Code Signing Certificate. HOW one gets whatever that thing is. If it needs to be transformed, tell us WHY and HOW. If there are variations for some reason, then LIST them out with the reasons so that a person can pick the correct path. INFORM the user what the proper tools are – if tools have been deprecated then list them elsewhere but NOT as part of the main stream of instructions. Put popular paths in place, such as “How to use a Code Signing Certificate with Visual Studio 2008″ and “How to sign Word 2007 Documents with a Code Signing Certificate” and so forth.
JasonP said 1 year ago:
As you are seeking specific information on the Code Signing Certificate other than what you have been able to find within our Help articles, I would recommend contacting our SSL Team directly to discuss your inquiries.
They are available 24/7 to assist you.