Signing
From KuneriLite wiki
Contents |
Getting your application Symbian Signed
Before starting the development, it is good to know the basics of Symbiansigned requirements and the process.
There are plenty of material about signing in the official Symbian website:
SymbianSigned Wiki
Complete Official Guideline
All signing options and related costs
All S60 3rd edition applications need signing. By default KuneriLite
creates automatically self-signed applications (*_signed.sis in project folder), which can be used freely in any phone, but since self-signed applications are not trusted,
user will be warned during install.
KuneriLite generates also unsigned version of the SIS, which cannot be installed into phone. Instead, it can be sent to Symbiansigned.com (Open Signed, for testing purposes, see below) for signing and after signing process, it can be installed into phone.
All applications are recommended to be signed with Symbian Signed certificate, before released in public. We recommend to follow "Express Signed" process using personal/company Publisher Id (TC TrustCenter Certificate, costs annually $200).
Briefly, these are the reasons when developer needs SymbianSigned:
1.Getting UID for generated application (and for official KuneriLite plug-ins)
2.Creating application using sensitive capabilities
- KuneriLite GPS and ringtone plug-ins require developer certificate, but for testing there are free tester applications available
- For testing: Developer certificate allows testing application only phones with IMEI's specifically listed by developer.
Open Signed Online/Offline process can be used to create tester applications.
3.For distribution purposes
- Submitting application to symbiansigned (via Express Signed) for certification
OR Submitting application to certified Test House for certification.
Submitting application to SymbianSigned process
After purchasing Publisher Id, you'll get TC TrustCenter certificate, which can be exported and generated into .cert and .key files.
Your Symbian account should change after identification, having
Open Signed Offline and Express Signing options, but you might need to tell
Symbian support to update it. Company contact information should be
filled properly and match with your Publisher Id information.
Input files with password into KuneriLite (rembember use original files received from TrustCenter, not Developer Certificate created with DevCert tool):
Then create the SIS.
TEST your application well so that it conforms to
Symbiansigned criteria.
IMPORTANT: Read these notes about Symbiansigned testing questions.
Then
EITHER submit application to Express Signed in SymbianSigned pages:
In Symbiansigned service, first you need to buy Content ID ($20 per application)
and then submit application using related link under "Submissions".
Submit all files they require.
It is important to verify that application conforms to all Symbiansigned criteria before submitting, to avoid possible implications.
Note:
In certificate pages you will be asked of information of capabilities used and related classes, then check out this page.
OR submit application to certified Test House
They have their own procedures.
Finally you'll get your application officially signed with Symbian root certificate (updated zip-file will be available for download).
Related costs
Express Signed is enough, if application conforms to Symbian Signed Test Criteria. Related costs are annually $200 for Publisher Id from TC TrustCenter and further costs $20 per application.
Trying to sign application using KuneriLite (free) Basic version
GPS plug-in, for instance, requires application signing (but you can also use free Kuneri's GPS tester).
It is not possible to sign application (with certificate), if it uses free version of KuneriLite plug-in(s), with Symbian Express or Open Signed Online,
BUT if you are just packaging your SWF and not using any plug-ins, it is possible.
This is because free version of KuneriLite plug-ins are created with UIDs belonging to Kuneri.
You have to request plug-ins, which are created with your UIDs, from Kuneri
(please check this out)
Signing application for development (testing) purposes
Option 1: Symbian Open Signed Online
Note: Open Signed Online signing process is meant only for testing SIS in limited amount of phones (certificate has IMEI lock).
If you don't have Publisher ID (TrustCenter certificate), you need to use Open Signed Online to sign generated SIS (you cannot use KL signing options).
This will be the case if:
- KL plug-ins requiring certificate is used. Currently only GPS plug-in, you need also to request new commercial/non-commercial version from Kuneri.
- if you are using UIDs from protected range.
But, if you just need to test plug-in functionality and you don't want go for Symbiansigned process, you can download and install free KL tester application and replace \data\others\trusted\[application\[app].swf file with your own swf-file
Before going Open Signed Online, obtain 1 personal UID for your application from
same Symbiansigned webpage.
Enter same personal UID to UID field. Then generate (unsigned) SIS (it will be *_unsigned.SIS file in project folder).
In Open Signed webpage, choose capabilities: Location NetworkServices ReadUserData WriteUserData (at least) and browse for unsigned version of the generated SIS.
Fill the rest information, proceed and signed SIS should be available for download after short period.
Hint: It is recommended to sign only once using Open Signed Online for development purposes. First generate and sign the application. Then install application into phone only once. Next time, copy changed SWF into target installation directory manually.
Option 2: Using Developer Certificate (Open Signed Offline)
In short, the process is:
1. Check out the Symbiansigned guideline.
2. If you are using free versions of KuneriLite plug-ins, you need to buy Publisher ID from TC TrustCenter.
For KuneriLite Commercial/Non-commercial with unique set of plugins, it is not required because all UIDs will belong to you.
3. Install DevCert tool from SymbianSigned.
4. Input the capabilities (all Basic caps) to DevCert tool.
5. Enter IMEIs of phone(s).
6. Submit produced .csr to Symbiansigned to obtain .cer file, using Open Signed Offline (assuming you have Publisher ID).
7. DevCert also produced .key file, enter .cer and key file into KL.
8. You can enter your own unprotected UIDs, but you don't need to,
because KuneriLite will generate UID's by default. This suits for R&D purposes,
but before releasing application in public use your personal UIDs,
preferably protected ones.
9. When developer certificate is used, you can install application into phone(s) with given IMEI.
Symbian Signed applications don't have such restriction.
