J2ME Signing with timestamping

[vishal.vpb]

Hello Developers,

I want to sign my J2ME midlets with time-stamp. i follow the following simple procedure.

1) Sign the J2ME apps using Thwate certificates.
2) Adding the time-stamp using following command which is executing successfully

jarsigner -tsa https://timestamp.geotrust.com/tsa -keystore <keystore_filename> <path to Applet (ie. C:\TestApplet.jar)> <alias_name>

My app is working fine if i don't time-stamped them, if I time-stamp the app, and execute it on My nokia-c3 device it says "Invalid Application delete?".

Can anyone please let me know how to overcome this.

Procedure for timestamp - https://search.thawte.com/support/ss...=AGENT_REFERAL

Please help me regarding this.

[im2amit]

My app is working fine if i don't time-stamped them, if I time-stamp the app, and execute it on My nokia-c3 device it says "Invalid Application delete?".

Please check the date&time settings on your Nokia C3, take a timestamp from device (it should be greater then the the Timestamp of the app certificate).
This might have caused due wrong timezone settings on your device also.

Try the to install the same app signed with TSA the next day on C3...

[vishal.vpb]

Try the to install the same app signed with TSA the next day on C3...

Thanks for replying..

No. its not working for me even though I have changed the Date on my device to 20th May 2012.

Changes occur after executing following command -
jarsigner -tsa https://timestamp.geotrust.com/tsa -keystore <keystore_filename> <path to Applet (ie. C:\TestApplet.jar)> <alias_name>

1) Two files get added in META-INF directory of jar file after executing above command.
2) Size of Jar file gets increased.
3) Some information is appended in MANIFEST.MF file of META-INF directory.

Thanks..

[bandarap]

Hi Visha.vpb,
Also check "Why doesn't my signed midlet work?" at http://javaverified.com/Why_doesnt_m...d_midlet_work2
verify your application with first and fourth common problem "midlet attributes are same in JAD and JAR manifest files, and date and time are not correctly set".

[vishal.vpb]

@ bandarap - I have check all the possibilities. But stiil getting same error.
Is it possible to timestamp java mobile apps.?
I dont want to re-submit all the apps when my certificates got expired.
Please help me.

[bandarap]

Hi vishal.vpb,

Procedure for timestamp - https://search.thawte.com/support/ss...=AGENT_REFERAL
Is for signing applets that don’t have JAD, but in mobile device you need JAD. Otherwise Nokia devices don’t recognize the jar.

In the same above link see the following text:“If you are Signing MIDlets please see solution SO16957 to sign using JADTool command line utilityUse jar to bundle your Applets or applications as a JAR file.”

To sign the midlet, follow the instructions given by thawte here . In that case you don't have to timestamp.

[vishal.vpb]

Hi bandarap,

I had followed the same steps...i.e. sign the app using jadtool and then time-stamp it.
Signed apps working fine. But after time stamping they are giving an error.
I want to time-stamp my signed apps in order to avoid any interruption in service after expiry of certificates.

Vishal B

[bandarap]

Hi Vishal,

In device prospective, signing the midlet is enough to get the required access. If you want to continue the service with thawte after certificate expires, you can contact thawte about this how they are handling timestamp for midlets. They didn’t mention anything about timestamp for midlet after signing. Your first post link timestamp is for applets.