View source

{{ReviewerApproved}}
{{NoteS}}

Carbide.c++ IDE offers inbuilt feature to create and sign the .sis file with Self-signed certificate or Developer certificate. See the images below:

* Step1 : Open your project in Carbide.c++
   Project >> Properties >> Carbide.c++ >> Build Configurations >> SIS Builder
[[Image:Step1.png]]



* Step2 :
   Project >> Properties >> Carbide.c++ >> Build Configurations >> SIS Builder >> Add
[[Image:Step2.png]]
{{NoteE}}


This article is specific to [[S60]] 3rd Edition development or newer. From [[S60]] 3rd Edition, which is based on [[Symbian OS]] 9, a user can install only signed applications.

If an application requires basic [[Capabilities|capabilities]] only, it can be signed with self-signed [[Certificates|certificate]]. Basic [[Capabilities|capabilities]] include [[LocalServices]], [[NetworkServices]], [[ReadUserData]], [[UserEnvironment]] and [[WriteUserData]]. Starting with S60 3rd Edition Feature Pack 2 release (aka S60 3.2) the [[Location]] capability can also be granted to self-signed applications.

An application that does not require any [[Capabilities|capabilities]] can also be signed with self-signed [[Certificates|certificate]]. The advantage of self-signing is that it's fast, since it's done locally on developer's machine and that a self-signed installable package can be installed on more than one device, i.e. no restriction applies (based on [[IMEI]] number, for example).

The drawback of self-signed [[Certificates|certificate]] is that a user will be prompted a warning dialog. It says that the application is not trusted and the user can decide whether or not to continue the installation. The warning dialog does not appear when the application is signed via [[Symbian Signed]].

Please note that self-signing works even if the application demands stronger capabilities than what is in the basic set, however, it won't install on the device.

Aside from the capability restrictions please note that you cannot self-sign applications having the UID3/SID in the protected range. In practice, during R&D stage you can use a random UID from the 0xE******* range but for the application release you must still use an UID allocated to you, for free, by Symbian. This UID will be in the 0xA******* range and can be obtained through the [https://www.symbiansigned.com/app/page/uid/requestUID Unprotected UID Allocation Request] form.

Following is the example which illustrates the Self-Signing procedure.

<br>

== Step-1 Creating Certificate and Keys ==

From your Desktop Screen: '''Start-&gt; Run -&gt; Cmd''' then go in your [[SIS|Sis]] file path using '''cd''' DOS command.<br>
<code>C:\HelloWorld\sis> makekeys -cert -password World123 -len 1024 -dname "CN=World User OU=Development OR=WorldCompany CO=FI EM=World@test.com" WorldKey.key WorldCert.cer</code> 

'''Note''': It is important the the above code be written on one line. This applies to the code below too.

This will create '''WorldKey.key''' and '''WorldCert.cer''' files which you will need to sign your '''HelloWorld.Sis''' file in the following statement.

'''Important:''' Versions of MakeKeys prior to Symbian 9.2 always generate certificates with a validity period of 1 year. This may be too short for released code, as it restricts the lifetime of the signed SIS files. You can [[Create a certificate using OpenSSL|create a certificate using OpenSSL]] to choose a different validity period, or use the update to MakeKeys provided by Symbian [http://www3.symbian.com/faq.nsf/AllByDate/0A641D4666011F9C002572250023F01C?OpenDocument here] to specify an alternative validity period.



== Step-2 Signing Application ==


<code>C:\HelloWorld\sis>signsis HelloWorld.sis HelloWorld.sis WorldCert.cer WorldKey.key World123</code> 


'''Note:''' Here you may find that '''World123''' is the password.

Finally you will get your Self-Signed certified '''HelloWorld.Sis''' file. Install it on the device. Have fun&nbsp;!!!

== Related articles ==
[[S60 SW installer troubleshooting]]

[[Category:Symbian_C++]] [[Category:How_To]] [[Category:Signing_and_Certification]] [[Category:Application_Signing]]