A Software Installation (SIS) file can be generated as an unsigned file, a self-signed or signed file. Self-signed and unsigned packages are considered to be unknown , and are installed by the Software Installer, depending on the security policy of the Symbian device.
If the SIS file is signed, the Software Installer validates the certificate chains and based on verification, installs the SIS file or aborts the installation.
Submit the certificate request to a Certificate Authority (CA) and receive an authenticated digital certificate.
Create a package (PKG) file containing all the elements required to create the installation file. For details see PKG File Format .
Run MakeSIS at the command prompt to create an unsigned SIS file. Specify the PKG file as input argument, as shown in the following example:
MakeSIS generates an unsigned SIS file.
Run SignSIS at the command prompt to sign the unsigned SIS file. Specify the unsigned SIS file as input, and public key certificate and private key as arguments, as shown in the following example:
Based on the certificate provided as input, SignSiS generates a signed SIS file. For details, see Signing
createsis create -cert trustedchain.pem -key eecertkey.key mypackage.pkg
The process of creating an installation file can be understood using the following illustration:
While creating a SIS file using the CreateSIS tool, if you do not specify the key or certificate on the command line the create method generates a key and a matching self-signed certificate, and uses it to sign the resulting SIS file.
The generated certificate and key is dumped into the current working directory as cert-gen.cer and key-gen.key files. If key-gen.key exists, the certificate and key filenames are indexed incrementally. That is, cert-genx.cer and key-genx.key , where x is the incremental index.
Note: The passphrase encryption is not an option. It must be provided with the -pass option. If this option is not specified, CreateSIS prompts for the passphrase during key generation.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License v1.0.