Midlet Attributes Used In Signing Midlet Suites; Creating The Signing Certificate; Inserting Certificates Into Jad - Motorola V3x Technical Manual

2 cameras; 320x240 display
Hide thumbs Also See for V3x:
Table of Contents

Advertisement

MIDlet suite, while the public key is provided as a x.509 certificate included in the
application descriptor (JAD).

MIDlet Attributes Used in Signing MIDlet Suites

Attributes defined within the manifest of the JAR are protected by the signature. Attributes
defined within the JAD are not protected or secured. Attributes that appear in the manifest
(JAR file) will not be overridden by a different value in the JAD for all trusted MIDlets. If a
MIDlet suite is to be trusted, the value in the JAD will equal the value of the corresponding
attribute in the manifest (JAR file), if not, the MIDlet suite will not be installed.
The attributes MIDlet-Permissions (-OPT) are ignored for unsigned MIDlet suites. The
untrusted domain policy is consistently applied to the untrusted applications. It is legal for
these attributes to exist only in JAD, only in the manifest, or in both locations. If these
attributes are in both the JAD and the manifest, they will be identical. If the permissions
requested in the HAD are different than those requested in the manifest, the installation
will be rejected.
Methods:
1. MIDlet.getAppProperty will return the attribute value from the manifest (JAR) if

Creating the Signing Certificate

The signer of the certificate will be made aware of the authorization policy for the handset
and contact the appropriate certificate authority. The signer can then send its
distinguished name (DN) and public key in the form of a certificate request to the
certificate authority used by the handset. The CA will create a x.509 (version 3) certificate
and return to the signer. If multiple CAs are used, all signer certificates in the JAD will
have the same public key.

Inserting Certificates into JAD

When inserting a certificate into a JAD, the certificate path includes the signer certificate
and any necessary certificates while omitting the root certificate. Root certificates will be
found on the device only.
Each certificate is encoded using base 64 without line breaks, and inserted into the
application descriptor as outlined below per MIDP 2.0.
MIDlet-Certificate-<n>-<m>: <base64 encoding of a
certificate>
Note the following:
one id defined. If an attribute value is not defined, the attribute value will return
from the application descriptor (JAD) if present.
89

Advertisement

Table of Contents
loading

Table of Contents