Developer Certificate

We recently applied for and received a devCert for a particular IMEI. My goal is to download an application onto the N95 and test using real hardware. It is not clear the process of signing the .sis file using the developer certificate. Please help.

Thanks

it is just the same as with any certificate, so you just make the sis first, and then use signsis to sign it with the certificate.

Hi,
As symbianyucca has mentioned you can sign your sis with the dev certificate just like normal certificates.
In case you want some more information on signing process check this wiki link
[url]http://wiki.forum.nokia.com/index.php/How_to_guide_for_creating/signing_sis_files[/url]

[QUOTE=LanceMProctor;477653]We recently applied for and received a devCert for a particular IMEI. My goal is to download an application onto the N95 and test using real hardware. It is not clear the process of signing the .sis file using the developer certificate. Please help.

Thanks[/QUOTE]
You can also sign by the Open Signed Online procedure, for the IMEI of your N95, the developer cert will not be required in that case.

[url]www.symbiansigned.com[/url]

Best Regards,
Croozeus

Hi,

Use this two commands...

[B]makesis [/B]your_pakaga_file.pkg

[B]signsis [/B]your_app.sis your_app.sisx the_certificate_with_the_specific_IMEI.cer the_key_with_the_specific_IMEI.key

And you can also set Carbide to build and sign your .sis file.
Project/Properties/Carbide.c++/Carbide Build Configuration/select a release configuration, and use "Add" on the SIS Builder panel. There you will easily manage to pick the .pkg file and your certificate.

Is there a way to probe the certificate for its enabled capabilities?

[QUOTE=LanceMProctor;480206]Is there a way to probe the certificate for its enabled capabilities?[/QUOTE]

See this [URL="http://wiki.forum.nokia.com/index.php/Listing_IMEIs_and_Capabilities_in_a_DevCert"]Listing IMEIs and Capabilities in a DevCert[/URL]

Ahhh ... thanks! All looks well with my certificate however I am having trouble opening the USB serial port on the N95 target. The open is failing with -46 KPermissionDenied (I assumed the issue was with my certificate ... not the case). I am using the ECUART comm module and Comm::1 as the port name. I have tried ACM::1 as well.

Ok ... problem solved. I THINK the problem had to do with mismatch capabilities in my mmp files. My application links in a static library that manages the data link between the MS and embedded platform. The library and the application had mismatched capabilities. After making the capabilities equilavent ... things started working.

Thanks!!

You THINK correctly. An application must have the same capabilities as any libraries it links to. If you don't then the code in the libraries trys to execute without the necessary capabilities and you get KErrPermissionDenied - as you've found.

Sorcery

P.S. Actually going the other way, a DLL can't be loaded by a process that has greater capabilities than it does. I don't think this generally applies for static libraries since they can't be signed and installed separately. Often a DLL will be signed with many more capabilities than it uses just so that applications that do have the capabilities can use it - in this scenario it's OK to have fewer capabilities in the application, so long as you know which ones the DLL is using.