Re: code signing problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



thanks for your comments. I just get it working - I followed the
tutorial on codeproject, but I thought the "sign" project property
would aldso authenticode sign my code which was wrong assumption - I
just have to use signtool directly and everythink works.

On Jul 19, 3:42 pm, dbgrick <dbgr...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Try using the Visual Studios test certificates. They can be found at
Microsoft Visual Studio 8\SmartDevices\SDK\SDKTools\TestCertificates
add the certificate under the Properties Devices tab by selecting the
authenticode signing check box and importing the certificate. You may need
to install the certificates on the device. You can do this using the
sdkcerts.cab file located in the sub directory from above. When you are
ready to release your project, go to Verisign and request a real
Mobile2Market certificate, sign you code, have Verisign sign it and you are
ready to go. I hope this helps.

Rick D.
Contractor

"Buthrakaur" wrote:
Hello,
I just tried to sign my assemblies with my newly generated
certificate, but I get just error message when compiling the assembly.
I was following this article:http://www.codeproject.com/useritems/signcode.asp
, generated my certificate with blank password and afterwards used the
*.pfx file for signing in the VS project settings.

The error message:
genasm.exe(1) : error There was an error initializing . Invalid
public key of assembly (HRESULT: 0x8013141E)

I also tried to generate new pfx certificate file directly from VS
project options dialog, but the compiler exception persists. Is there
any method how to get the signing working?

I used a snk file succesfully before, but I need to create the
provisioning file for WM devices and didn't found any method how to
get public part of the certificate to be able to get the SHA and
base64 values for building _setup.xml provisioning file. Is there any
method how to install certificate from a snk file on the device?

And another question - I created some helloworld application which I
was able to sign in VS and compile succesfully. The output exe file is
but without any signed certificate. The only working method is using
the signtool.exe utility, which will really sign the assembly and add
the certificate to the end of file (it is visible in HEX-editor). Is
the sign dialog in VS just for strong name signing and not for code
signing?


.



Relevant Pages

  • IT WORKS !!
    ... I was signing the wrong assembly - signing the serializers and not the ... Copy assemblies to your server NB I do steps 5-8 on a postbuild.cmd file ... drop certificate SqlReportHandlerCert ... create login SqlReportHandler from certificate SqlReportHandlerCert ...
    (microsoft.public.sqlserver.security)
  • Re: Programmatically Signing DLL
    ... Authenicode signing adds ~ 1 kbyte of data, it wouldn't be a big deal to ... > What kind of certificate do we need to buy to allow programmatic ... IE5+ can properly verify the validity of an Authenticode signature (build into ... As I mentioned before, the CAPICOM install is a no-brainer, fast install, no reboot ...
    (microsoft.public.security)
  • "Unknown Publisher" with kernel-mode driver signed with VeriSign c
    ... I am using a certificate from VeriSign but no WHQL certificate. ... VeriSign Class 3 Code Signing 2009-2 CA ... SHA1 hash: 599F2301A083500D52D0917CCCCC8FE86F8DF3B7 ...
    (microsoft.public.development.device.drivers)
  • Re: Programmatically Signing DLL
    ... key on it and sign a .DLL before it goes into production. ... > Dim Signer, SignedCode ... What kind of certificate do we need to buy to allow programmatic ... signing and validation of a DLL using VC++. ...
    (microsoft.public.security)
  • Re: .NET 2.0: code access security / authentication
    ... > There are two types of code signing used for .NET assemblies: ... > signing and authenticode signing. ... > publisher" issue is authenticode signing, ... you need a code signing certificate ...
    (microsoft.public.dotnet.security)