Symbian quick signature process details

The mobile phone program developed on the Symbian operating system must be digitally signed before it can be successfully installed on the mobile terminal. The digital signature mechanism can effectively prevent the spread of malicious Mobile Phone programs and protect the legitimate rights and interests of software developers and mobile users. So, how do I implement the Symbian digital signature? Currently, there are three main methods: Open signed, certified signed, and express signed ).
There are two types of open signatures: Open singed online and open singed offline ). Open Signature allows developers to easily sign the SIS program for testing or personal use. With the open signature, you no longer need the publisher certificate (publisher ID), content certificate (Content ID), and Symbian signed account, and are free of charge. Developers can use this method to conveniently, quickly, and free one-time signature services for a single device limited by a mobile phone serial number (IMEI. Therefore, open signatures are especially suitable for debugging and testing programs at the early stage of development. After all the programming and testing work is completed, mobile phone programs need to be promoted. Since open signatures are subject to IMEI restrictions, signatures are required for each installation on a mobile phone, which is very cumbersome.
The authentication signature uses the B-type root certificate of Symbian to sign the sisfile. You can use the Symbian OS flag. After the signature, the program cannot be modified. Otherwise, the program cannot be installed. To authenticate the signature, you must purchase the publisher ID and register the Symbian signed account. The authentication signature must be tested by an independent testing organization on the mobile phone program. The signature can only be signed after the test is passed. The testing fee is specified by the testing company. The testing fee for standard Symbian applications is generally 185 euros (about 2000 RMB ). The test cycle is generally 4 to 5 business days. If the test fails, modify the test according to the feedback from the testing company, and submit the modified application to the testing company for retesting until the test passes. The fee for re-testing is determined by the testing company. mphasis (Chinese contact, Shanghai Office) is priced at 160 euros (about 1730 yuan ). The signed programs do not have IMEI restrictions. You can use more capabilities (capabilities) and install them on all mobile phones. However, it takes some time and money to perform independent tests to authenticate the signature, which is not conducive to the rapid deployment of the program. Therefore, Symbian provides a quicker signature method-quick signature.
Quick signature also uses the B-type root certificate of Symbian to sign the sisfile. the symbol of Symbian OS cannot be used, and the program cannot be modified after the signature; otherwise, the program cannot be installed. You must purchase the publisher ID and Content ID for the quick signature and register the Symbian signed account. Quick signatures do not require independent testing, But Symbian may randomly perform random sampling. The tested program will be sent to an independent testing agency for testing by Symbian. The cost will be borne by Symbian. If the program does not pass the test, Symbian will deregister your quick signature qualification, which means that you must authenticate the signature next time, symbian will restore your quick signature qualification. Quick signature programs do not have IMEI restrictions and can be installed on all mobile phones. The following describes the entire process of quick signature.
1. Purchase publisher ID. Domestic users generally purchase from wotong, Shenzhen at a cost of about 1600 RMB.
The validity period is one year. You need to renew the subscription after expiration and provide a new publisher ID. If you do not need to update the software one year later, there is no other development requirement, you do not need to apply for a new publisher ID for the publisher. At the time of purchase, you must provide the company's business license, telephone bill, technical contact ID card and email, etc. A certificate will be issued within one to two working days after the identity authentication and payment. The following describes how to obtain a certificate: Open IE, select "content" in "Internet Options" of "Tools", and click "certificate" to view the signature certificate, we need to export the certificate that has been installed in IE. pfx format, and then use the Certificate Format Conversion Tool. the pfx certificate is converted to a two-Certificate file, and the private key and password of the certificate are also remembered, which will be used later when signing the sisfile. In addition, when you obtain the publisher ID, Symbian will provide you with a password to revoke the certificate for certificate leakage.
2. Purchase the Content ID. The fee is about $20. Make sure that the content ID exists before the quick signature is used. The Content ID is valid for 10 years. The sisfile packaged with Content ID is valid for 10 years. The Content ID is stored in your Symbian signed account. Each time you perform a quick signature on an sisfile, a content ID is used.
3. Apply for uid. You can apply for a protected uid field number in the Symbian signed account. Each account can apply up to 20 uid field numbers every day (the UID field number is free of charge ). After applying for the UID field number, replace all the original uid numbers in the program.
4. self-testing. Replace the UID, re-compile and generate the sisfile, use the open signed signature, install it on the mobile phone, and perform standardized testing on the program according to the latest Symbian signed test standard. During the test, you must record the testing status of each clause, whether the test is successful, failed, or meets the exception clause. Enter the test result when submitting the quick test.
5. Package. After the test is passed, use the publisher ID to re-sign the sisfile. The signing command is signsis MyApp. sis MyApp. sisx mycert. CER mykey. key mypassword, in which mypassword is the private key password of the certificate mentioned in step 1st. Use the signature verification tool to verify the newly signed sisfile and confirm that the sisfile has been correctly signed. Package the following sisfile named mongopkgfile named readme.txtand userguide.txt into a zip file. Among them, readme.txtmainly introduces some specific things during program release. userguide.txt mainly introduces how to use the program. Note: The packaged ZIP file cannot contain the path. Otherwise, it will fail to be submitted for a quick test.
6. Submit a quick signature. Log on to the Symbian signed account, upload the packaged ZIP file, follow the wizard of express signed, and finally submit and download.
Pay special attention to the following points during the quick signature process:
1. When registering a Symbian signed account, you must use an enterprise email address; otherwise, registration may fail. The Enterprise mailbox used to register the Symbian signed account must be the same as the one provided by the technical contact when applying for the publisher ID.
2. After a request for publisher ID is sent, the operating system cannot be reinstalled until the publisher ID is obtained. Otherwise, the publisher ID may not be successfully received.
3. The program version number mentioned by readme.txt in the zippack file must be the same as the version number in the PKG file and the version number in the program dialog box. Otherwise, the test may fail.
4. If another sisfile is embedded in the sisfile, the embedded sisfile must have been signed. Otherwise, the quick signature may fail.