eclipse签名（eclipse签名）.docVIP

eclipse签名（eclipse签名） About the digital signature of the MIDlet Suite Starting with the Eclipse 0.7.0 release, you began to support signing MIDlet using a password. This document provides background information on digital signature processing, describes the manual flow of digital signatures for MIDlet suites, and illustrates how EclipseME is handled. background knowledge Basic steps Using EclipseME for digital signatures Password management Simulation operation Reference material -------------------------------------------------------------------------------- background knowledge In the MIDP 1 specification, all MIDlet uses a sandbox safe mode to run. Thus, in essence, MIDlet can only access the API set defined in the MIDP 1 specification, and libraries that are packaged in the same MIDlet suite. MIDP 2 (JSR-118) introduced the concept of trusted (trusted) and untrusted (untrusted) concepts into the MIDlet suite. An untrusted package runs in the same restrictive environment as MIDP 1 - all available API sets can only be part of the MIDP specification. The trusted package can be given more API access to the device. Also, as part of the MIDP 2 specification, some standard API also need authorization to access. For example, an untrusted MIDlet suite must be able to access javax.microedition.io.HttpConnection API, but the system requires the user to verify that the MIDlet suite is allowed to use the API. On the other hand, trusted MIDlet suites can be granted access to the API without requiring explicit user authorization, and access to API that prohibits untrusted MIDlet access. Basic steps to digitally sign a MIDlet Suite The basic steps of digital signature are as follows: Include the list of permissions required by your MIDlet suite in the JAD file and in the manifest (listing) Gets the appropriate key / certificate pair to digitally sign During the deployment of the MIDlet suite, the final digital signature step is performed Include the list of permissions required