Table of Contents
Advertisement
Displaying of Permissions to the User
Permissions will be divided into function groups and two high-level categories, with the
function groups being displayed to the user. These two categories are Network/Cost
related and User/Privacy related.
The Network/Cost related category will include net access, messaging, application auto
invocation, and local connectivity function groups.
The user/privacy related category will include multimedia recording, read user data
access, and the write user data access function groups. These function groups will be
displayed in the settings of the MIDlet suite.
Only 3
rd
Operator and manufacturer permissions will be displayed for each MIDlet suite, but
cannot be modified by the user.
Trusted MIDlet Suites Using x.509 PKI
Using the x.509 PKI (Public Key Infrastructure) mechanism, the handset will be able to
verify the signer of the MIDlet suite and bind it to a protection domain which will allow the
MIDlet suite access to the protected API or function. Once the MIDlet suite is bound to a
protection domain, it will use the permission defined in the protection domain to grant the
MIDlet suite access to the defined protected APIs or functions.
The MIDlet suite is protected by signing the JAR file. The signature and certificates are
added to the application descriptor (JAD) as attributes and will be used by the handset to
verify the signature. Authentication is complete when the handset uses the root certificate
(found on the handset) to bind the MIDlet suite to a protection domain (found on the
handset).
Signing a MIDlet Suite
The default security model involves the MIDlet suite, the signer, and public key
certificates. A set of root certificates are used to verify certificates generated by the signer.
Specially designed certificates for code signing can be obtained from the manufacturer,
operator, or certificate authority. Only root certificates stored on the handset will be
supported by the Motorola V3x handset.
Signer of MIDlet Suites
The signer of a MIDlet suite can be the developer or an outside party that is responsible
for distributing, supporting, or the billing of the MIDlet suite. The signer will have a public
key infrastructure and the certificate will be validated to one of the protection domain root
certificates on the handset. The public key is used to verify the signature of JAR on the
88
party and untrusted permissions can be modified or accessed by the user.
Advertisement
Table of Contents
