| RE: [buckminster-dev] create.eclipse.jnlp.product issues |
I found that my problem (A) (jar resources in jnlp not signed by same certificate) is caused by the fact that the eclipse jars (3.3 or later) are signed by eclipse ( CN="Eclipse.org Foundation, Inc", OU=Digital ID Class 3 - Java Object Signing, O="Eclipse.org Foundation, Inc", L=Ottawa, ST=Ontario, C=CA), while my own code is signed by my certificate, and the eclipse 3.2 jars are not signed at all. On the internet they suggest to split up the jars per signer, and bundle them in jnlp files like that, but how can i do this with the 3.2 / 3.3 jars? Or they suggest to unsign everything and simply resign it with my own certificate, but i have not yet found a tool to unsign jars properly. Can you give some feedback on this? DISCLAIMER: Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
<<winmail.dat>>