Reply to Thread

Re: Code signing confusion

Hi Rich,

I think you are 100% right with 1) or 2).

BTW, I requested a 3yr certificate for a customer today. New Windows 10 Pro virtual machine, standard settings. Opened IE and accepted all the requested security settings. Certificate request worked without any problem.

Friedrich

Re: Code signing confusion

Hello,

again, this is not caused by any "Lindersoft doorway". This is the original Sectigo order page on Sectigo servers (they are processing quite a few thousand certificate requests per day).

BTW, you have to ask the WebTrust how to handle dbs's. I know that there are very strict rules in town.

Friedrich

Re: Code signing confusion

I had no choice to find another means to obtain a digital signing certificate since the Lindersoft doorway simply doesn't work no matter how hard I attempt finding a fix for the unsupported browsers and failure of IE to send the request.

The problem I am now having has to do with getting a certificate under a fictitious business name (dba) as opposed to my own personal name. I am sure I'm not the only software developer that uses a business moniker (aka "fictitious name" or "dba") for their small business software development. Is there any "trick" or method for a John Smith to get the certificate to display "ABC Software" as opposed to "John Smith"?

Re: Code signing confusion

Surely someone must know how to get past the "Your browser did not send a certification request" error?
Seems like the problem might be:
1) An anti-virus thing blocking I/E, or
2) One of the many ActiveX settings that can be tweaked under the “Security level for this zone”, or
3) Maybe Microsoft really did kill this fashion of obtaining code signing certificates!
-- Rich F.

Re: Code signing confusion

Hindsight is 20/20, but when the Lindersoft customer attempts this process for the first time, none of what you have clarified is clear or "obvious." That is my point.

Re: Code signing confusion

This "Lindersoft" banner just tells you that your certificate request makes use of the Lindersoft partner discount (e.g. $200 instead of $500 for a 3yr certificate).

If you go directly to the trust-provider.com website then it displays the standard Sectigo logo (no discount). It's always the same order page for all partners, resellers, etc. worldwide.

https://secure.trust-provider.com

Friedrich

Re: Code signing confusion

Originally Posted by linder

So this is a question for Microsoft and Sectigo, right?

Lindersoft provides a secure doorway to some unknown page, which I (and I suspect others) would have no idea was not associated with Lindersoft. The doorway page is trust-provider.com, not Sectigo.

Look at the snapshot below. Why would I suddenly become aware that Lindersoft is not associated with the certificate purchase process when the Lindersoft logo/banner is prominent at the top of this doorway page, which when the user clicks "Next" results in an utter failure to proceed?Attachment 5118

Re: Code signing confusion

What I am trying to say is that we (or any other non-Microsoft and non-Sectigo company) do not have any control over this process.

Friedrich

Re: Code signing confusion

Sorry, but what does SetupBuilder or Lindersoft have to do with this? We provide access to discounted Sectigo certificates. Not more and not less. You can request the same certificate without our discount ($200 instead of $500) gateway, but it will be the SAME Sectigo (Authenticode) ordering process.

So this is a question for Microsoft and Sectigo, right? Again: you request an original Sectigo code-signing certificates from Sectigo (we redirect you to their servers and you pay to Sectigo).

https://support.comodo.com/index.php...ng-certificate

Friedrich

Re: Code signing confusion

Originally Posted by linder

BTW, IE is still available in Win10 (Select Start and enter Internet Explorer).

Microsoft is removing IE according to Microsoft. You can confirm this here: https://www.howtogeek.com/846237/her...tely%20removed.

Relevant quote from the above article:
The next stage in the plan will start with the February 2023 security update for Windows 11, which is currently scheduled for February 14, 2023, and a preview build will be available on January 17. With that update, Internet Explorer icons on the Start Menu and taskbar will be removed, and any files or shortcuts that open in IE will be opened with Edge instead.

So my original question still stands... What is a Setupbuilder customer supposed to do when all the browsers that one might have cannot be used to purchase a code signing certificate via the Lindersoft doorway page?