|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Jun 10, 2013, at 8:20 AM, Steve Kann wrote:
Signed code contains several digital signatures:
• If the code is universal, the object code for each slice (architecture) is signed separately. This signature is stored within the binary file itself.
• Various components of the application bundle (such as the Info.plist file, if there is one) are also signed. These signatures are stored in a file called _CodeSignature/CodeResources within the bundle.
Neither of which appear to apply for a jnlp file.
Curious, when you say this worked on the local machine where did the signature go?
I was thinking one possibility for this would be to keep the jnlp signature in a file separate on the server. For <MyApp>.jnlp have the associated signature as <MyApp>.sig or something.
Java Web Start when it starts running could parse the server URL out of the jnlp download and attach the signature. Again thinking extended attributes was the mechanism this might not of been all that tough. But what is the mechanism? Where did your signature go?
This probably wouldn't do anything for you on dynamic jnlp either. Since a change in the jnlp should mean generating a new signature.
trz nio.2 for OS X http://www195.pair.com/mik3hall/index.html#trz
HalfPipe Java 6/7 shell app http://www195.pair.com/mik3hall/index.html#halfpipe
AppConverter convert Apple jvm to openjdk apps http://www195.pair.com/mik3hall/index.html#appconverter
_______________________________________________ Do not post admin requests to the list. They will be ignored. Java-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
|>JNLP signing requirement. (From: Steve Kann <email@hidden>)|
|>Re: JNLP signing requirement. (From: Steve Kann <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.