Symbian developer community

 
Home > Wiki > Symbian Signed Tools
wiki

Symbian Signed Tools

From Symbian Developer Community

Jump to: navigation, search

This article gathers together information on the most commonly used tools during the signing process. This page will give you a quick overview of each tool, along instructions on where you can find it.

The tools break down largely into three categories, tools which are needed for signing, those which help with testing and others which are useful for troubleshooting.

Some of the tools discussed are owned and hosted by the Symbian Signed Team at the Symbian Foundation, whereas some are third party tools owned and hosted elsewhere. Whilst the sections of this article on tools owned by the Symbian Foundation will be largely maintained by the team at the Symbian Foundation, it's expected that members of the community will contribute to this page by adding details of tools which they have found useful during the signing process.

Contents

Signing Tools

Publisher ID export tool

This tool is required by the Symbian Signed process to convert your private key and public certificate into a format MakeSIS/SignSIS can use. You will need to do this to either sign your SIS file with your Publisher ID prior to signing using either Express Signed or Certified Signed.

Two versions of this tool are available, and you should choose the correct one depending on whether you have a TC TrustCenter or a Verisign ACS Publisher ID. Please download tcp12p8 for TC TrustCenter Publisher Ids File:TC-ConvertP12.zip. Please download File:Vs pkcs.zip for Verisign ACS Publisher Ids.

DevCertRequest

This tool is needed to request a developer certificate for using Open Signed Offline to sign your application. This tool is owned, and maintained by the Symbian Foundation and is available for download from this site. It is currently only available for Windows PCs: File:DevCertRequest 2.3.zip

SignSIS and MakeSIS tools

The SignSIS and MakeSIS tools are included with the Symbian SDK. You will need one of these tools to sign a .SIS file locally on your machine.

You will need the tool to use a Developer Certificate (Open Signed Offline) to sign your .SIS file for testing and will also need to use this tool to sign your .SIS file with your Publisher ID before submitting it for Express Signed or Certified Signed.

Currently, these tools are only available as part of your SDK.

Certificate Manager Plugin

This is a plug-in for Carbide which will allow you to manage your developer certificates. It also contains an improved version of DevCertRequest for requesting developer certificates to use with Open Signed Offline.

Please download the Certificate manager plugin for Carbide: File:Symbian Certificate Manager Plug-in for Carbide.c++.zip

Developer Certificate contents tool

This tool is really useful for debugging problems with IMEIs within a Developer Certificate. It lists the IMEIs in a Developer Certificate and also flags any IMEIs that may be problematic.

Listing IMEIs and Capabilities in a DevCert

VerifySymbianSigned

Please note that the VerifySymbianSigned tool will not recognise Publisher IDs issued after 1st December 2009. This is because the intermediate certificate used to check the signature of the sis file has been changed. Alternatively you can use the latest version of the signsis tool with the -p flag to see that your sis file has been signed with a valid Publisher ID.

VerifySymbianSigned is a command line tool that runs on the PC and it is used to verify the signing status of a SIS file. A file can either be Publisher ID signed, Developer Certificate signed or Symbian Signed.  Please download VerifySymbianSigned here: File:VerifySymbianSigned v2.4.zip

Tools for testing

File Browsers

File storage load/stress testing can be simulated by uploading a file/s to fill the selected mass storage device.

Profiler tools

Any kind of application profiler/task list (only Required for UIQ applications)

LowMem Tool

The Low Memory Tool will test application start-up during low memory situations.  If the application does not start due to lack of memory it indicates to the user that there is not enough memory.

Please download the LowMem user guide [here|Symbian Signed Tools^LowMem.zip]

Other useful tools

In this section, we have included some links to other tools which you may find useful during the testing and signing process.

What is in my SIS

This web site allows you to upload your SIS file to find out information about what files are contained within the SIS file and what capabilities these files are using. It also shows the certificate chain for the SIS file. http://www.whatisinmysis.com/

Sign that SIS\! - a Firefox Plugin

Reduce the time to submit an application through Open Signed Online with this plugin. This uses prefill form fields and is useful for those wanting to demo or test an application using Open Signed Online. The current version is .1 and in order to get the plugin, you have to go through Mozilla. [[1]]

UnSIS

File:UnSIS Setup.zip - unpacks pre EKA2 SIS files.

Retrieved from "http://developer.symbian.org/wiki/index.php/Symbian_Signed_Tools"

Comments

Supriyaakg said…

I have created a self signed package, with Adobe Mobile Packager 1.1, that contains a .pkg, a metadata file, an SIS, a png of the logo and its SVG. I have tested the app on my E71 and it works fine. I do not understand the need to avail a Publisher ID for a Certified Signed certificate and then submit my app to https://www.symbiansigned.com/app/page/isvApplicationSubmissionWizard.do. What are the steps needed to submit the app to Nokia for testing and publishing to the Ovi Store? I dont understand how should I proceed. Please help.

--Supriyaakg 06:00, 15 February 2010 (UTC)

Danm said…

You should ask your questions over in the forum (http://developer.symbian.org/forum/forumdisplay.php?f=5) rather than here as we scan the forums regularly to provide answers...

--Danm 10:12, 15 February 2010 (UTC)

Sign in to comment…