Creating The Rsa Sha-1 Signature Of The Jar; Signature Of The Jar; Authenticating Amid Let Suite - Motorola MOTORAZR maxx V6 Developer's Manual

Java ME Developer Guide
Chapter 8 - MIDP 2.0 Security Model
When inserting a certificate into a JAD, the certificate path includes the signer certi-
ficate and any necessary certificates while omitting the root certificate. Root certific-
ates 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:
<n>:= a number equal to 1 for first certification path in the descriptor, or 1 greater
than the previous number for additional certification paths. This defines the sequence
in which the certificates are tested to see if the corresponding root certificate is on
the device.
<m>:= a number equal to 1 for the signer's certificate in a certification path or 1
greater than the previous number for any subsequent intermediate certificates.
8.16 Creating the RSA SHA-1

signature of the JAR

The signature of the JAR is created with the signer's private key according to the
EMSA-PKCS1 -v1_5 encoding method of PKCS #1 version 2.0 standard from RFC
2437. The signature is base64 encoded and formatted as a single MIDlet-
Jar-RSA-SHA1 attribute without line breaks and inserted into the JAD.
It will be noted that the signer of the MIDlet suite is responsible for its protection do-
main root certificate owner for protecting the domain's APIs and protected functions;
therefore, the signer will check the MIDlet suite before signing it. Protection domain
root certificate owners can delegate signing MIDlet suites to a third party and in
some instances, the author of the MIDlet.
8.17 Authenticating a MIDlet Suite
DRAFT - Subject to Change
[60/201]