jar-signing

问题 Can someone show me how pom file should look like to create a jar file with applet which depends from some other jars is it possible to have one jar as applet, and how to sign it? 回答1: If you would like your classes and the dependencies to appear in one jar file , you should use either the assembly plugin or the one-jar plugin before the jarsigner. I have the following working setup with the assembly plugin, it will produce the normal (signed) jar and a ${artifactId}-${version}-jar-with

问题 We coded a java applet and signed it through a Certificate Authority, Entrust. When the applet is deployed through any browser, we can see in java console logs that a request is made to the CA: network: Connecting http://ocsp.entrust.net/ with proxy=DIRECT security: OCSP Response: GOOD However, our client has some computers in an intranet without internet connection. So, is there a way to avoid any internet request to CA server? 回答1: You will find this option from Java Control Panel >>

问题 Another try to open a message here My company wants to use the deployment rule set for multiple java versions usage. Currenly we have 1.6.0_13, 1.7.0_51 and 1.8.0_66 Java 8 is what selected in the System tab of the java control home User tab consists of java 6, 7 and 8 all the settings in deployment.properties are default and point to correct locations or values env variables set java_home ="C:\Program Files (x86)\Java\jdk1.8.0_66\bin" path = set to correct locations The steps i followed are

问题 i can't understand where problem lies to run applet in browser when deploy my project accordind to http://docs.oracle.com/javase/tutorial/deployment/applet/deployingApplet.html http://www.coderanch.com/t/258307/Applets/java/Signing-JAR-certificate jar manifest code Permissions: all-permisisons Application-Name:------------ Butt still error in browser Unknown publishers Security warning ExceptionInInitializerError AccessControlException is problem to signing jar of my project? i use 3rd party

问题 I have an app on Google Play for years that has seen countless updates. The latest update (the first one in a while) fails to install for some people, they simply get the "Package not signed correctly" error message. It works for my Android devices I have at home. I'm building and signing with a custom build system that basically boils down to calling ant release , followed by jarsigner -verbose -keystore $(keystore) -storepass $(storepass) $(appname).apk $(alias) zipalign -v 4 $(appname).apk

问题 I have submitted and published an app in the Google Play store. I did not receive any errors when I uploaded my binary. Now, I am receiving reports from some (not all) customers stating that they are getting the following error when installing our App: "Package file was not signed correctly" When I try to replicate this error myself (using a Nexus 7 reset to factory settings), however, everything goes smoothly. This seems to be similar to the issue described in this question, but the accepted

问题 I have submitted and published an app in the Google Play store. I did not receive any errors when I uploaded my binary. Now, I am receiving reports from some (not all) customers stating that they are getting the following error when installing our App: "Package file was not signed correctly" When I try to replicate this error myself (using a Nexus 7 reset to factory settings), however, everything goes smoothly. This seems to be similar to the issue described in this question, but the accepted

问题 SO I am testing a Rest OAuth implementation. My testing tool will send the HTTP Request, but I need to prepare the Authorization header. What I need: I want a valid Authorization Header What I have: All the headers except the oauth_signature I also have the 2 secrets, the token_secret and the consumer_secret. I also posses the access_token. So It really boils down to, having to sign this request. How do I do that? Summary : I simply need to populate the oauth_signature portion of the

问题 I'm trying to programmatically verify that a jar file has not been obviously tampered with. I have 2 use cases I want to prevent. 1) Modifications of existing classes 2) additions of new classes in the jar I signed the jar using jarsigner. When I verify either of the above cases with jarsigner it works like I would expect. When I try to do it programmatically using the samples in How to verify a jar signed with jarsigner programmatically or How to verify signature on self signed jar? however,

问题 I used jarsigner to sign my jar file. But I got a warning: Warning: This jar contains entries whose signer certificate will expire within six months. How can I make it never expire or expire in a longer time? 回答1: Specify the required number of days in the -validity parameter to keytool. Addendum: -validity is an option to keytool. keytool -genkey -alias sawyer -validity 1234 -dname "…" After you create the new key, use its unique alias with jarsigner to sign your JAR. 来源： https:/