Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Symbian Signed Tools

From Wiki
Jump to: navigation, search

This article gathers together information on the tools most commonly used during the Symbian Signed process. It give a quick overview of each tool and information 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 are owned and hosted by the Symbian Signed Team at the Symbian Foundation, the remainder are third party tools owned and hosted elsewhere. We hope that members of the community will contribute to this page by adding details of tools which they have found useful during the signing process.


Signing Tools

Publisher ID export tool

You must use this tool to when you receive a Publisher ID certificate from TC TrustCenter. It extracts your private and public keys from the certificate and converts them into a format that you can use to get your applications Symbian Signed.

You can download the tool here. You can find instructions for using it (and for purchasing a Publisher ID certificate) on this page.

You will need the keys whenever you use MakeSIS or SignSIS (see below) to create a SIS for Express Signed or Certified Signed.

A second version of Publisher ID tool is available here for Verisign ACS publisher IDs.

Note.pngNote: Publisher IDs issued by Verisign are no longer supported by Symbian Signed although your existing certificate might still be accepted with limited functionality. New Publisher IDs must be obtained from TC TrustCenter.

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

Developer Certificate contents tool

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

Listing IMEIs and Capabilities in a DevCert


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

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^]

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.

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]


File:UnSIS - unpacks pre EKA2 SIS files.

Tools that are no longer used


DevCertRequest tool was historically used to request developer certificates from the Symbian Signed site. Developer certificates are now requested directly through the site interface, so this tool is no longer required.

Licence icon cc-by-sa 3.0-88x31.png© 2010 Symbian Foundation Limited. This document is licensed under the Creative Commons Attribution-Share Alike 2.0 license. See for the full terms of the license.
Note that this content was originally hosted on the Symbian Foundation developer wiki.

This page was last modified on 27 September 2012, at 04:35.
78 page views in the last 30 days.