Comments on: Code signing Visual Studio 2010 extensions (VSIX)

By: Anonymous

Anonymous — Thu, 09 Jun 2011 08:23:00 +0000

You need and Authenticode cert… which it sounds like you have. Maybe an
issue with the final package?

By: Stefan Wenig

Stefan Wenig — Thu, 09 Jun 2011 08:15:00 +0000

ok, now i’m confused. what kind of certificate would you – as the tool’s author – need, and how does this affect me?
I’m using our own Go Daddy certificate, and like I said, it works for VS, but not for Code Gallery.

intended for:
Ensures software came from software publisher
Protects software from alteration after publication
2.16.840.1.114413.1.7.23.2

issued to: rubicon informationstechn gmbh
issued by: Go Daddy Secure Certification Authority
valid from 2010-04-13 to 2013-04-13

issuer stmt: https://certs.godaddy.com/anonymous/repository.seam

sig. algorithm: sha1RSA
hash alg.: sha1
key usage: Digital Signature (80)
thumbprint alg.: sha1

cert path:
Go Daddy Class 2 Certification Authority
Go Daddy Secure Certification Authority
rubicon informationstechn gmbh

any idea what’s going on?

thanks for your help!

By: Anonymous

Anonymous — Wed, 08 Jun 2011 17:51:00 +0000

Unfortunately I believe my code signing certificate expired and I didn’t
properly sign it the first time (with a time server).

By: Stefan Wenig

Stefan Wenig — Wed, 08 Jun 2011 15:27:00 +0000

Great tool! The signed vsix works as expected for local installation.

However, if I try and load it into VS Code Gallery, I get: “Invalid Certificate in VSIX”. So I have to provide a link instead. Do you have any experience with Code Gallery? Any idea if your tool causes this, or something else? We use a GoDaddy authenticode cert.

Here’s the thing: http://licensemanager.codeplex.com/releases

Any help appreciated!

Thanks, Stefan

By: Dew Drop – March 3, 2010 | Alvin Ashcraft's Morning Dew

Dew Drop – March 3, 2010 | Alvin Ashcraft's Morning Dew — Wed, 03 Mar 2010 12:45:46 +0000

[...] Code signing Visual Studio 2010 extensions (VSIX) (Jeff Wilcox) [...]