CodeI needed to sign a MIDlet and deploy it on a Nokia Series 60 phone (i.e. 6630, 6680 etc) so the user doesn't constantly get security alerts. I figured (hoped?) this might be a fairly simple task since any useful application is likely to need access to restricted functionality. It turns out I was very, very wrong. There is virtually no information on how to sign and deploy an application on the web. Anyway here are the steps I took to get my MIDlet signed and installed!
Get required software
Get and install the Java SDK (JDK) from Sun (you should already have this)
Get and install the Java Wireless Toolkit (WTK) also from Sun
Optionally get and install Ant and Antenna to allow you to automate your build
Create and import a certificate
You need to use keytool (from the JDK)
I used the following command keytool -genkey -alias {myalias} -keyalg RSA -validity 365
This will prompt you for a keystore password, enter your keystore password (if you have an existing keystore) or the one you want to use if you don't have one yet
Fill in all the prompts about location/company name etc
Run keytool -list to see your new certificate
Next you must export the certificate so you can import it to your phone
Run keytool -export -alias {myalias} -file mycertificate.crt
Import the certificate into your phone, in Windows XP SP2 I could do this by right clicking the file and selecting "Send to Bluetooth Device"
Build and package the application
Use javac to build your MIDlet paying special attention to your classpath and bootclasspath options (otherwise preverification will fail). I also set target to 1.1 and source to 1.3
Generate your JAD file the critical attributes in the JAD are MIDlet-Jar-URL, MIDlet-Jar-Size, MIDlet-Permissions we also included MIDlet-Icon, MicroEdition-Configuration, MicroEdition-Profile, MIDlet-Name, MIDlet-Push-1, MIDlet-Icon, MIDlet-Descriptionn and MIDlet-Version
Generate the MANIFEST.MF file based on your JAD, you must remove MIDlet-Jar-Size and MIDlet-Jar-URL
Both these tasks can be completed using the wtkJad Antenna task
Package and preverify the app using the wtkPackage Antenna Task you must set the classpath and bootclasspath properties correctly otherwise Preverification will fail
Sign the application
Sign the Application using jarsigner
Run jarsigner -keystore {mykeystore} -storepass (mypassword} {myjar} {myalias}
Now you have a signed jar you need to update the MIDlet-Jar-Size in your JAD
Now add the certificate to the JAD using JadTool.jar from the WTK
Run java -jar JadTool.jar -addcert -alias {myalias} -storepass {mypassword} -keystore {mykeystore} -inputjad {myinputjad} -outputjad {myoutputjad}
Now add the signature to the JAD again using JadTool.jar
Run java -jar JadTool.jar -addjarsig -alias {myalias} -jarfile {myjar} -storepass {mypassword} -keypass {mypassword} -keystore {mykeystore} -inputjad {myinputjad} -outputjad {myoutputjad}
You can now deploy this to a webserver with the MIME types set correctly and download it to your phone and it will be a trusted 3rd party application
原文地址 http://www.spindriftpages.net/pebble/dave/2005/06/20/1119275880301.html
------------------------------------------------------------------------------------------------------
It’s been a long time since the original MIDlet jar signing (a tutorial) and it’s about time I collated all the feedback into a revised tutorial. Let me know what you think.
Get required software
Java SDK (JDK) from Sun (you should already have this)
Java Wireless Toolkit (WTK) also from Sun
Optionally get and install Ant and Antenna to allow you to automate your build (I’d strongly recommend these)
Import an existing certificate (if you have one)
If you’ve purchased a certificate from Verisign (or another provider) you need to import the certificate into your J2SE keystore.
Try using the following command keytool -import -alias {myalias} -file {mycertificate} (I haven’t been able to test this since I don’t have a proper certificate)
Run keytool -list to see your new certificate
Next you must export the certificate so you can import it to your phone
Run keytool -export -alias {myalias} -file mycertificate.crt
Import the certificate into your phone (see below for details)
Create and import a new (test) certificate
You need to use keytool (from the JDK)
I used the following command keytool -genkey -alias {myalias} -keyalg RSA -validity 365
This will prompt you for a keystore password, enter your keystore password (if you have an existing keystore) or the one you want to use if you don’t have one yet
Fill in all the prompts about location/company name etc.
C:\j2sdk1.4.2_08\bin>keytool -genkey -alias company -keyalg RSA -validity 365
Enter keystore password: password
What is your first and last name? [Unknown]: My Name
What is the name of your organizational unit? [Unknown]: company
What is the name of your organization? [Unknown]: company
What is the name of your City or Locality? [Unknown]: location
What is the name of your State or Province? [Unknown]: location2
What is the two-letter country code for this unit? [Unknown]: GB
Is CN=My Name, OU=company, O=company, L=location, ST=location2, C=GB correct? [no]: yes
Enter key password for (RETURN if same as keystore password):
Run keytool -list to see your new certificate
Next you must export the certificate so you can import it to your phone
Run keytool -export -alias {myalias} -file mycertificate.crt
Import the certificate into your phone (see below for details)
Build and package the application
Use javac to build your MIDlet paying special attention to your classpath and bootclasspath options (otherwise preverification will fail). I also set target to 1.1 and source to 1.3
Generate your JAD file the critical attributes in the JAD are MIDlet-Jar-URL, MIDlet-Jar-Size, MIDlet-Permissions we also included MIDlet-Icon, MicroEdition-Configuration, MicroEdition-Profile, MIDlet-Name, MIDlet-Push-1, MIDlet-Icon, MIDlet-Description and MIDlet-Version
Generate the MANIFEST.MF file based on your JAD, you must remove MIDlet-Jar-Size and MIDlet-Jar-URL
Both these tasks can be completed using the wtkJad Antenna task
Package and preverify the app using the wtkPackage Antenna Task you must set the classpath and bootclasspath properties correctly otherwise Preverification will fail
Sign the application
Sign the Application using jarsigner
Run jarsigner -keystore {mykeystore} -storepass (mypassword} {myjar} {myalias}
Now you have a signed jar you need to update the MIDlet-Jar-Size in your JAD
Now add the certificate to the JAD using JadTool.jar from the WTK
Run java -jar JadTool.jar -addcert -alias {myalias} -storepass {mypassword} -keystore {mykeystore} -inputjad {myinputjad} -outputjad {myoutputjad}
Now add the signature to the JAD again using JadTool.jar
Run java -jar JadTool.jar -addjarsig -alias {myalias} -jarfile {myjar} -storepass {mypassword} -keypass {mypassword} -keystore {mykeystore} -inputjad {myinputjad} -outputjad {myoutputjad}
Deployment
Deploy this to a web server with the MIME types set correctly and download it to your phone and it will be a trusted 3rd party application
You can also deploy applications to phones by sending the JAR & JAD to the phone over Bluetooth or Infrared or a cable depending on your phones features. On Nokia phones the files
appear in your SMS Inbox
Installing the Certificate on the phone
Import the certificate into your phone, in Windows XP SP2 I could do
this by right clicking the file and selecting "Send to Bluetooth Device",
you should be able to send files by cable or Infra Red (IR) too. NB: I
haven’t found anyway of importing a certificate on a Series 40 phone
Once the certificate is installed it needs to be authorised for
"Application Installation". On my phone (Nokia 6680) this is under
Tools->Settings->Certificate Management->Trust Settings, I turned on
everything but I think "Application Installation" is all you need
Common Problems
Application not installed using the JAD: The application is only trusted if it is installed using the JAD, the application will still install from the jar but it won’t be trusted.
Application trust settings not set: Once your application is installed you need to specify how much trust to give it (it doesn’t get all permissions by default). On a Nokia Series 60 phone these are found under the App. Manager.
Root certificate missing from phone: The Java Verified certificate and/or Verisign certificates are missing from some phones check under Tools->Settings->Certificate Management for the relevant certificate
Authorization Failed: - There are a whole host of possible reasons behind this here are the ones I’ve come across
Certificate missing from phone, double check your certificate is installed and has been marked as trusted for application installs in Certificate Management
Reboot: Uninstall the application completely then reboot your phone try taking the battery and SIM out too, often things get themselves in a twist, especially if you’ve been re-installing a lot without uninstalling first
JAD/JAR mismatch: Double check the application size in the JAD, remember it’s the number of bytes that is important NOT the size on disk
Browser cache: If you’re installing over the air make sure you clear your browser cache before installing
I’ve heard but not verified that line breaks in the MIDlet-Permissions can cause problems but it seems ok to me on Nokia 6680/6630/6230i (could be firmware dependent?)
The MIDlet-Permissions attribute is the cause of a lot of problems (especially since the documentation is often wrong/missing or different depending on the phone), try leaving it out first and add permissions in one at a time. Some phones will complain about permissions they don’t support, some will ignore them
There is a bug in some early Nokia 6600 firmwares that stop the install of trusted MIDlets
Certificate not valid yet: If you generated the certificate yourself it may have a start validity date of tomorrow, also if your PC and phone dates are different you may be outside the period of validity of the certificate
No certificate management on Series 40 phones, you can install a signed application but behavior is strange with self signed certificates
JadTool problems: I haven’t experienced any of these issues but lots of other people have
"I have issues if I try to use the jadtool manually. I have a certificate chain and can’t seem to get the second certificate added to the JAD file using any WTK jadtool. The interesting part however is that I can successfully sign the midlet using any of the same WTK GUI interfaces - they add the second certificate correctly. My steps:
Use 1.4.2_06 jarsigner.exe to sign jar
Use WTK (2.2 or 2.3 beta) jadtool to addcert with certnum 1
If I call jadtool to addcert with certnum 2 the same certificate is inserted as cert 1-2 I’m assuming I am doing something incorrectly since the WTK gui seems to be working just fine"
"I received a post on the KVM news group on the topic that states there is a bug in the jadtool and the author claims to have filed a bug report and posted a patch: http://archives.java.sun.com/cgi-bin/wa?A2=ind0508&L=kvm-interest&F=&S=&P=9858 One interesting note that was also posted was that the cert JAD params are static so once you get them from the WTK correctly you can put them statically in the ant script."
"I am trying to sign a MIdlet for Nokia 6620 device. I am using a Verisign Code Signing certificate that actually contains two certificates (User and Intermediate CA). I am using the WTK 2.2 signing tool. Do you know if this tool support two certificates when signing ? The signature is added to the JAD file with two certificates but I have been getting security error when installing. I have checked on the device and there are different root certificates installed for Verisign but it still fails !
"If you want, you can download the sprintpcs developer kit as it supports dual certs (http://developer.sprintpcs.com). However, I never got that cert to work on the Nokia (6620/cingular) phone, although it does work on sprint phones (with developer root enabled). Ultimately, I only got things to work by creating the cert as described in this blog and installing that on the phone. Bizarrely, even though the root cert for my versign-signed cert *was* on the 6620 phone, it still would never install my MIDlet as you would think it should."
Old phones (6230/i, 6682) don’t support x509 certificates, WPKI has been suggested as a possible solution but I haven’t investigated this
Socket connections can be problematic (http://discussion.forum.nokia.com/forum/showthread.php?t=68306 ) possibly due to the WAP infrastructure and the services provided by an operator. HTTP is a much safer protocol to use
"Go online and check application validity": Yes/No. If I click on yes button the phone I get the following error: "Certificate revoked for this application" and the installation fails. To rectify this go to Tools -> Manager -> Menu -> Settings -> Online Certif Check [ On / Off / Required] There is also a Default address setting. If the online control setting is required, the check will fail, if there is no default address. see http://discussion.forum.nokia.com/forum/showthread.php?t=71071
Trust Domains
There are 4 different trust domains in MIDP2 (manufacturer, operator, trusted third party, and untrusted). Trusted Third Party is the only one of any use to us really.
It gives the following options on my Nokia 6680 (Vodafone UK):
Network Access: Not Allowed, Ask every time, Ask first time
Messaging: Not Allowed, Ask every time App
Auto-Start: Not Allowed, Ask every time, Ask first time
Connectivity: Not Allowed, Ask every time, Ask first time, Always allowed
Multimedia: Not Allowed, Ask every time, Ask first time
Read User Data: Not Allowed, Ask every time, Ask first time, Always allowed
Edit User Data: Not Allowed, Ask every time, Ask first time, Always allowed
These settings are defined by the operator and the phone manufacturer and therefore vary between phone, manufacturer and operator.
Unresolved Problems
I managed to sign the JAD with this format using J2ME WTK utilities, but when trying to install it on the device I get a message "Application authentication failed 909".
Sample JAD
MIDlet-Jar-URL: MyApp.jar
MIDlet-Jar-Size: 201365
MIDlet-Name: MyApp
MIDlet-Vendor: EC1M
MicroEdition-Profile: MIDP-2.0
MicroEdition-Configuration: CLDC-1.1
MIDlet-Icon: logo.png
MIDlet-Push-1: sms://:6553,net.ec1m.MyApp.midp.MyAppMIDlet,*
MIDlet-Description: MyApp MIDlet
MIDlet-Permissions: javax.microedition.io.PushRegistry,javax.microedition.io.Connector.sms…
MIDlet-Version: 1.0.67 MIDlet-1: MyApp, logo.png,net.ec1m.MyApp.midp.MyAppMIDlet
MIDlet-Certificate-1-1: MIICODCCAaECBEKqpfswDQYJKoZIhvcNAQEEBQAwYz…=
MIDlet-Jar-RSA-SHA1: EUsAch/…/hEZOsJsiCjBOhNs/3FSw4=
Sample Manifest
Manifest-Version: 1.0
MIDlet-Name: MyApp
Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
MIDlet-Push-1: sms://:6553,net.ec1m.MyApp.midp.MyAppMIDlet,*
MIDlet-1: MyApp, logo.png, net.ec1m.MyApp.midp.MyAppMIDlet
MicroEdition-Configuration: CLDC-1.1
Ant-Version: Apache Ant 1.6.2
MIDlet-Icon: logo.png
MIDlet-Vendor: EC1M
MIDlet-Permissions: javax.microedition…
MIDlet-Version: 1.0.67
MicroEdition-Profile: MIDP-2.0
MIDlet-Description: MyApp MIDlet
Sample Ant Build File
I’ve put our EC1M ant build file up on our website to (hopefully) make all this a little easier for you.
Other Resources
This FAQ on the Nokia Forum is worth a read. (Thanks chortya for the link)
Posted in /Technology.
Tagged with /Technology.
By dave June 18, 2006