We usually use a corporate signing tool that keeps an audit trail of what's
been signed. That's for released code, however for internal builds we've
used signtool.exe and a test certificate. When I tried this today, I found
it wasn't working, with this
SignTool Error: An error occurred while attempting to sign: tsjLnEML.dll
SignTool Error: ISignedCode::Sign returned error: 0x800B010A
A certificate chain could not be built to a trusted root authority.
This is since a recent update to signtool.
Well, a test cert will never have a trusted root authority, does this mean
you can no longer sign with test certificates?
MikeS
On Tue, Sep 24, 2013 at 2:52 PM, Tristan Reeves <[email protected]> wrote:
> Thanks Anthony.
>
> On Tue, Sep 24, 2013 at 10:44 AM, Anthony Tjea <[email protected]>
> wrote:
> >
> > I've used GoDaddy in the past.
> >
> > http://www.godaddy.com/ssl/code-signing-certificate.aspx?ci=13314
> >
> >
> > You have to go through a verification process before they issue you it.
> > Same with most others.
> >
> > To create a test cert.
> >
> > http://msdn.microsoft.com/en-us/library/ff699202.aspx
> >
> >
> > Anthony
> >
> > ________________________________________
> >
> >
> >
> >
> >
> > On 23/09/13 7:27 PM, "Tristan Reeves" <[email protected]> wrote:
> >
> >>Hi List,
> >>Title says it all...can anyone advise what steps need to be taken to
> >>get a code-signing certificate? It seems quite a murky subject for
> >>some reason. At least for me...then again perhaps it's my google-fu
> >>which is lacking.
> >>
> >>I suppose one uses SignTool.exe (on windows) to actually do the signing
> >>(?)
> >>
> >>
> >>Thanks,
> >>Tristan.
> >
>
--
Meski
http://courteous.ly/aAOZcv
"Going to Starbucks for coffee is like going to prison for sex. Sure,
you'll get it, but it's going to be rough" - Adam Hills
