Symbian 3rd signature, self-signed, Development Certificate, manufacturer level, capability set, acs id, billing, sensitive API

The purpose of this article is to introduce the signature process for the third edition of Symbian, which is also very confusing for many Symbian developers. I hope you will not be confused after reading this article, but also want to understand the signature of the Nokia mobile app!

1. access capabilities in 3rd are restricted and unrestricted. 60% of the APIs are unrestricted. you can install them on any compatible mobile phone using a self-signed certificate signature. Package: makesis *. PKG *. sis Signature: signsis *. sis *. sisx *. CER *. key 111111 generate self-signed certificate: makekeys-cert-Password 111111-len 1024-dname "cn = China ou = development or = Datang Mobile Ltd lsg@datangmobile.cn" LSG. key LSG. cer.

2. other restricted capabilities can be obtained through "Developer Certificate", "Symbian signature", "authorized production/platform approval". The development certificate must be applied on www.symbiansigned.com. The application process will be discussed later.

3. You can apply for a free development certificate with only one IMEI number, that is, one mobile phone. If you have multiple mobile phones, you need to apply for multiple certificates. Then you can write a BAT file signature for processing.

4. A Development Certificate supports 20 IMEI numbers, but the application requires an acs id. However, the acs id is charged for about $100.

5. the development certificate does not support all APIs. That is to say, some very sensitive APIs not only need to develop certificates, but also need to apply for sensitive capability development from the manufacturer. This application is free of charge, but requires Nokia's consent, and provide the company's business license.

6. Let's look back at the capability set description:
Unlimited: 60% API.
Apply for a free development certificate:

Readuserdata, writeuserdata, networkservices, localservices, userenvironment, location, readdevicedata, writedevicedata, powermgmt, Su

Rroundingsdd, protserv, trustedui, and swevent.
Approved by Nokia: [DRM, TCB] vendor, [allfiles, commdd, diskadmin, multimediadd, networkcontrol] capability request.

7. API capability definition:
Networkservices: used to use a mobile network, such as making a call or sending a text message.
Localservices: used to send or receive messages through USB, infrared, and Bluetooth.
Readuserdata: allows reading user data. System servers and application engines can freely apply this restriction to their data.
Writeuserdata: Allows Writing user data. System servers and application engines can freely apply this restriction to their data.
Location: the location information of the mobile phone.
Userenvironment: allows access to real-time confidential information of users and their nearby environments.
Powermgmt: allows you to interrupt any process in the system or switch the machine status (disable the device ).
Swevent: allows you to generate or capture keyboard and pen input events.
Readdevicedata: allows reading system device driver data.
Writedevicedata: Allows writing data to the drive of the system device.
Surroundingsdd: A logical device driver that provides peripheral device input information.
Tustedui: differentiate the UI of the "normal" application and "trusted" application. When a "trusted" application displays content on the screen, a "normal" application cannot forge it.
Protserv: allows the server application to register with a protected name. The protected name is "!" .
Networkcontrol: allows modification or access to network protocol control.
Multimediadd: allows access to all multimedia device drivers (sound, camera, etc.
DRM: permission to access the content protected by DRM.
TCB: allow access to the/sys and/resource directories on the terminal.
Commdd: allow access to the driver of the communication device.
Diskadmin: Allows disk management, such as formatting a drive.
Allfiles: allows all files in the system to be visible and allows you to write files under/private.

8. Steps for applying for a development certificate:
1. log on to www.symbiansigned.com with your username and password.
2. Download: certificate request tool: devcertrequest
3. Install and run the certificate request tool step by step as required until the *. CSR file is generated.
4. Upload the CSR file to www.symbiansigned.com.
5. Download the *. Cer file from the Internet. The entire process is over.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? Postid = 1717729