Technical information

July 15, 2008 G24 KJAVA User’s Guide D-1
Appendix D: MIDlet Signing
General
There are two types of MIDlet signing:
• Generic signing
• Bound signing
Generic Signing
Generically signed MIDlet can be downloaded to all G24 units. Once a MIDlet is tested and ready
for deployment to production, it will be generically signed.
Only the manufacturer (Motorola Wireless Modules) can generically sign a MIDlet.
To request a generic signature, refer to [e-mail].
Bound Signing
Bound signed MIDlet can be downloaded to a specific G24 unit. In development phase, in order
to download a trusted MIDlet to a G24 unit, it should be "bound signed".
All the tools and documentation for establishing "bound signing" procedure are located in the
"BoundSignBundle.zip" file, located at
http://developer.motorola.com/products/embeddeddevices/g24.
The document "Signing a MIDlet with a BOUND Certificate (External Release)" details all the
necessary steps to receive a "bound certificate".
The above procedure allows signing a MIDlet using a special certificate, called "bound
certificate". Such a certificate is tied to the UID of the G24 unit.
Below is a summary of all the steps necessary for the developer to follow, in order to establish a
"bound signing" procedure:
1. Download the "BoundSignBundle.zip" file.
2. Set up the digital signing environment by performing steps 2.2.1, 2.2.2, 2.2.3 and 2.2.4 from
the "Signing a MIDlet with a BOUND Certificate (External Release)" document.
3. Create a Certificate Signing Request and collect UIDs by performing steps 10, 11, 12 from
chapter 2.2.5 of the above document.
4. Fill in all the "G24_Bound_Cert_Request_Form_182-1.doc" will all the UIDs collected in
the previous step (maximum 10 UIDs per request).