Tool for signing jars

hi
Is there any tool with gui form. so that we can just fill values and click on a button and the applet is signed thanx alot

I've had great success with JDeploy - you can download it here:
http://www.tiobe.com/jdeploy.htm
IF not, you might want to check out the resource listing at google:
http://directory.google.com/Top/Computers/Programming/Languages/Java/Development_Tools/Deployment/?il=1
Best regards,
Bj�rn B�rresen

Similar Messages

Multiple jnlp's for signed jars

Hi,
I'm trying to solve the issue where you have several different certificates trying to sign the jars ... I've found out that you can just add extentions to your main jnlp and add the jars there.
Problem: I have loads of jars, all with different certificates.
At the moment I just generate my jnlp by usign a template, and entering $dependencies to list all jars in the file. That didn't work (JAR resources in JNLP file are not signed by same certificate), so I added my main jar in the main jnlp, and all the other jars in the extended jnlp, which is not working. Probably because (correct me if I'm wrong) I have to split every jar with another certificate into another jnlp ?
Is there any way I can split up the signed jars without having to add them manually in the jnlp file ?
Edited by: ReggieBE on May 16, 2008 1:17 AM

Oh, and I'm using webstart-maven-plugin from mojo.codehouse.org ;)

Tools for signing a pdf form using a stylus

I have created a form using Life Cycle Designer ES 8.2 and have included some signature boxes for uses to sign, on a Windows 7 o/s. Instead of using digital signatures I would like the users to scribe on a professionally looking and performing wireless pad using a stylus tool/pen. I have sourced such a device call the Wireless Bamboo pad from Wacom, but have read some mixed reports about the sensitivity and responsiveness of this device.
Does anyone have any experience of using such a device and could suggest what would be the best device to use?

Sorry about that, I assumed it was the Android version. Adobe Reader should work just fine then, assuming that signing with the pencil tool is sufficient. This is the same as the "Apply Ink Signature" tool. The document will just need to be Reader-enabled.

Tool for building jars

Hello,
I need to package an application (actually an Applet) that is dependent on many many class files in many many packages in our environment.
Is there a tool that can find all the dependent classes my Applet depends on and put them in a jar with the correct classpath
thanks

I've had great success with JDeploy - you can download it here:
http://www.tiobe.com/jdeploy.htm
IF not, you might want to check out the resource listing at google:
http://directory.google.com/Top/Computers/Programming/Languages/Java/Development_Tools/Deployment/?il=1
Best regards,
Bj�rn B�rresen

Signed Jars

I have a web based project that includes numerous iamges. As a result of the images I must sign the jar files. However, to date I have been unsuccessful. I have reviewed the threads and deployment information and would appreciate a straightforward way to accomplish this with Net Beans (the signing function there has not worked for me as well). I would appreciate any assistance.

If you can place the images inside your jar file and load them from there or place them on a server that hosts crossdomain.xml (*exactly* this file http://static.flickr.com/crossdomain.xml) in the root directory of it's domain, then you do not need to sign your jar file. If you cannot do either of these things and the images must be hosted on a different server than the one hosting your jars, then read on.
Do not try to use the javafxpackager command line tool to sign jars as that does not currently work => this issue can be tracked here: http://javafx-jira.kenai.com/browse/RT-18246
Signing documentation is here =>
http://docs.oracle.com/javafx/2.0/deployment/packaging.htm#BABJGFBH
http://docs.oracle.com/javafx/2.0/deployment/javafx_ant_task_reference001.htm#CIAFJGAB
But you have already read all that.
Signing requires the following steps.
1. Generate a Certificate Signing Request (CSR).
2. Submit the CSR to a Certificate Authority (CA).
3. The CA will generate a code signing certificate for you.
4. Package your application as a bunch of jar files.
5. Sign the jar files using your code signing certificate.
If you are just using a self signed certificate and you are already using NetBeans, then NetBeans can do all of this for you.
Here are the steps I used to sign a JavaFX project consisting of multiple Jar files using NetBeans nightly build 201112120600
1. Right click Project and choose Properties.
2. Project Properties | Libraries | Compile |Add Library... and add your dependent jars.
3. Project Properties | Packaging
Check Compress JAR File
Check Build JAR after Compiling
Check Copy Dependent Libraries
Do not check Binary Encode JavaFX CSS Files as that might be buggy.
4. Project Properties | Deployment
Check Request unrestricted access
Signing Certificate: Edit...
a) choose Self-signed by a generated key OR
b) use your own keystore if you have a certificate from a trusted public CA.
Download Mode for Libraries: Use the mix of eager and lazy appropriate for your app. Signing wise, it doesn't matter as all of the jars need to be signed anyway.
5. Project Properties | Run
Configuration | New... | Configuration Name => enter browser
Application Class | Browse... choose your Application's main class.
Check Use Preloader if you have one (the preloader jar will be signed). If you are having difficulties with basic signing, get that to work first before enabling the Preloader.
Select Run | in Browser
Set a Width and Height for the page.
Leave Web Page empty until you get an empty web page with your app in it to work.
Choose the Web Browser you want to launch the app in.
Press OK.
6. Select the browser config from the drop down combo and hit the run arrow.
Netbeans will compile your app, package it, generate a self signed certificate, sign all of your application's jars and launch the application in a browser.
A trick to getting all of the above to work more than one time, is to make sure that you close the browser tab after you have finished testing and before you try to run again, otherwise NetBeans seems to fail with weird errors because the distribution files get locked by the app running inside the browser under Windows.
If you are still stuck, you can try opening this JavaFX project which uses self-signed jars in NetBeans 7.1 RC2 or later => http://willow-browser.googlecode.com/files/willow-src-prerelease-0.1-netbeans-project.zip

Restriction for signed applet

Hi all,
i signed applet which is trying to modify file tmp.txt on client machine. Is there any opportunity for client to forbid this action for signed applet?
I tried use policy file but i was unlucky. It is ok for unsigned applet but what about signed one?
Thank you for your response.
benky

you need to install the jre, and place the win32.dll at JavaSoft\JRE\1.3.1_06\bin, that properties file place at JavaSoft\JRE\1.3.1_06\lib, comm.jar at JavaSoft\JRE\1.3.1_06\lib\ext\
and in ur code try to use it to open ur com port
public String test() {
String drivername = "com.sun.comm.Win32Driver";
try
CommDriver driver = (CommDriver) Class.forName(drivername).newInstance(); driver.initialize();
catch (Throwable th)
{* Discard it */}
drivername = "javax.comm.*";
try
CommDriver driver = (CommDriver) Class.forName(drivername).newInstance(); driver.initialize();
catch (Throwable th)
{* Discard it */}
portList = CommPortIdentifier.getPortIdentifiers();
while (portList.hasMoreElements()) {
portId = (CommPortIdentifier) portList.nextElement();
if (portId.getPortType() == CommPortIdentifier.PORT_SERIAL) {
if (portId.getName().equals("COM2")) {
//if (portId.getName().equals("/dev/term/a")) {
try {
serialPort = (SerialPort)
portId.open("SimpleWriteApp", 2000);
} catch (PortInUseException e) {}
try {
outputStream = serialPort.getOutputStream();
} catch (IOException e) {}
try {
serialPort.setSerialPortParams(9600,
SerialPort.DATABITS_8,
SerialPort.STOPBITS_1,
SerialPort.PARITY_NONE);
} catch (UnsupportedCommOperationException e) {}
int i=0;
while(true)
try {
messageString="hi";
System.out.println(i++);
outputStream.write(messageString.getBytes());
} catch (IOException e)
System.out.println(e);
messageString=String.valueOf(e);
return messageString;
and yet u need to signed the applet
1. Compile the applet
2. Create a JAR file
3. Generate Keys
4. Sign the JAR file
5. Export the Public Key Certificate
6. Import the Certificate as a Trusted Certificate
7. Create the policy file
8. Run the applet
Susan
Susan bundles the applet executable in a JAR file, signs the JAR file, and exports the public key certificate.
1. Compile the Applet
In her working directory, Susan uses the javac command to compile the SignedAppletDemo.java class. The output from the javac command is the SignedAppletDemo.class.
javac SignedAppletDemo.java
2. Make a JAR File
Susan then makes the compiled SignedAppletDemo.class file into a JAR file. The -cvf option to the jar command creates a new archive (c), using verbose mode (v), and specifies the archive file name (f). The archive file name is SignedApplet.jar.
jar cvf SignedApplet.jar SignedAppletDemo.class
3. Generate Keys
Susan creates a keystore database named susanstore that has an entry for a newly generated public and private key pair with the public key in a certificate. A JAR file is signed with the private key of the creator of the JAR file and the signature is verified by the recipient of the JAR file with the public key in the pair. The certificate is a statement from the owner of the private key that the public key in the pair has a particular value so the person using the public key can be assured the public key is authentic. Public and private keys must already exist in the keystore database before jarsigner can be used to sign or verify the signature on a JAR file.
In her working directory, Susan creates a keystore database and generates the keys:
keytool -genkey -alias signFiles -keystore susanstore -keypass kpi135 -dname "cn=jones" -storepass ab987c
This keytool -genkey command invocation generates a key pair that is identified by the alias signFiles. Subsequent keytool command invocations use this alias and the key password (-keypass kpi135) to access the private key in the generated pair.
The generated key pair is stored in a keystore database called susanstore (-keystore susanstore) in the current directory, and accessed with the susanstore password (-storepass ab987c).
The -dname "cn=jones" option specifies an X.500 Distinguished Name with a commonName (cn) value. X.500 Distinguished Names identify entities for X.509 certificates.
You can view all keytool options and parameters by typing:
keytool -help
4. Sign the JAR File
JAR Signer is a command line tool for signing and verifying the signature on JAR files. In her working directory, Susan uses jarsigner to make a signed copy of the SignedApplet.jar file.
jarsigner -keystore susanstore -storepass ab987c -keypass kpi135 -signedjar SSignedApplet.jar SignedApplet.jar signFiles
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5. Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5: Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
In her working directory, Susan uses keytool to copy the certificate from susanstore to a file named SusanJones.cer as follows:
keytool -export -keystore susanstore -storepass ab987c -alias signFiles -file SusanJones.cer
Ray
Ray receives the JAR file from Susan, imports the certificate, creates a policy file granting the applet access, and runs the applet.
6. Import Certificate as a Trusted Certificate
Ray has received SSignedApplet.jar and SusanJones.cer from Susan. He puts them in his home directory. Ray must now create a keystore database (raystore) and import the certificate into it. Ray uses keytool in his home directory /home/ray to import the certificate:
keytool -import -alias susan -file SusanJones.cer -keystore raystore -storepass abcdefgh
7. Create the Policy File
The policy file grants the SSignedApplet.jar file signed by the alias susan permission to create newfile (and no other file) in the user's home directory.
Ray creates the policy file in his home directory using either policytool or an ASCII editor.
keystore "/home/ray/raystore";
// A sample policy file that lets a JavaTM program
// create newfile in user's home directory
// Satya N Dodda
grant SignedBy "susan"
permission java.security.AllPermission;
8. Run the Applet in Applet Viewer
Applet Viewer connects to the HTML documents and resources specified in the call to appletviewer, and displays the applet in its own window. To run the example, Ray copies the signed JAR file and HTML file to /home/aURL/public_html and invokes Applet viewer from his home directory as follows:
Html code :
</body>
</html>
<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
width="600" height="400" align="middle"
codebase="http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#Version=1,3,1,2">
<PARAM NAME="code" VALUE="SignedAppletDemo.class">
<PARAM NAME="archive" VALUE="SSignedApplet.jar">
<PARAM NAME="type" VALUE="application/x-java-applet;version=1.3">
</OBJECT>
</body>
</html>
appletviewer -J-Djava.security.policy=Write.jp
http://aURL.com/SignedApplet.html
Note: Type everything on one line and put a space after Write.jp
The -J-Djava.security.policy=Write.jp option tells Applet Viewer to run the applet referenced in the SignedApplet.html file with the Write.jp policy file.
Note: The Policy file can be stored on a server and specified in the appletviewer invocation as a URL.
9. Run the Applet in Browser
Download JRE 1.3 from Javasoft
good luck! [email protected]
i already give u many tips, i use 2 weeks to try this to success, hopw that u understand that, a result of success is not important, the process of how to get things done is most usefull!

SunOne ignores signed jars -- bug?

This is a follow-up to http://softwareforum.sun.com/NASApp/jive/thread.jsp?forum=69&thread=18672.
The use of signedBy grant blocks appears to be broken, at least for signed jars that are deployed as part of an ear file. I created and signed a small jar that attemps to do a few normally forbidden things, then added these entries to the server.policy file:
keystore "file:${/}C:${/}Sun${/}AppServer7${/}codesign.keystore";
grant signedBy "codesign" {
permission java.util.PropertyPermission "*", "read,write";
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
Then I included the jar in a small enterprise app in which an EJB called the "forbidden" methods. In spite of the entires in server.policy, the code still fails due to AccessControlExceptions.
Running with -Djava.security.debug=policy reveals:
[04/Apr/2003:09:56:46] WARNING ( 2176): CORE3283: stderr: policy: getPermissions:
[04/Apr/2003:09:56:46] WARNING ( 2176): CORE3283: stderr:      PD CodeSource: (file:/C:/Sun/AppServer7/domains/domain1/server1/applications/j2ee-apps/cms_3/./lib/SignedJarTest.jar <no certificates>)
Note the <no certificates>
Running the class from the command line -- using the exact same jar, and using the SunOne JVM and server.policy file -- is successful.:
java -cp ./Sun/AppServer7/domains/domain1/server1/applications/j2ee-apps/cms_3/lib/SignedJarTest.jar -Djava.security.manager -Djava.security.policy=C:/Sun/AppServer7/domains/domain1/server1/config/server.policy -Djava.security.debug=policy com.seabase.scratch.crypto.SignedJarTest
policy: getPermissions:
PD CodeSource: (file:/C:/Sun/AppServer7/domains/domain1/server1/applicat
ions/j2ee-apps/cms_3/lib/SignedJarTest.jar [
Version: V1
Subject: CN=Patrick Jones, OU=DOE Project, O=SEA, L=New Orleans, ST=Louisiana,
C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: com.sun.net.ssl.internal.ssl.JSA_RSAPublicKey@72ffb
Validity: [From: Tue Apr 01 12:34:18 CST 2003,
               To: Sun Jul 20 01:34:18 CDT 2003]
Issuer: CN=CA, OU=DOE Project, O=SEA, L=New Orleans, ST=Louisiana, C=US
SerialNumber: [    4a821187 ]
... etc
SunOne evidently ignores the fact that this jar is signed. This appears to be a bug.

Java Plug-in 1.6.0_26
Using JRE version 1.6.0_26-b03 Java HotSpot(TM) Client VM
User home directory = C:\Users\dbladorn
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
exception: exit(-1).
ExitException[ 4]java.lang.RuntimeException: exit(-1)
     at com.sun.javaws.Main.systemExit(Unknown Source)
     at com.sun.javaws.security.AppPolicy.grantUnrestrictedAccess(Unknown Source)
     at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
     at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
     at sun.plugin2.applet.JNLP2Manager.prepareLaunchFile(Unknown Source)
     at sun.plugin2.applet.JNLP2Manager.loadJarFiles(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Exception: ExitException[ 4]java.lang.RuntimeException: exit(-1)

Signing Jars For JWS

My company just got me a Java coding signing cert from Verisign for signing the jar files used by our JWS application. At first I could not get cert to inport using keytool. So based on a suggestion from someone, I imported the cert into IE to verify it was a valid cert. This worked fine, so I exported the cert from IE in 509 format. I was then able to import the cert into a keystore. The problem is when I attempt to sign my jar files I get the error: jarsigner: Certificate chain not found for: signfiles. signfiles must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.
What does this mean, and how do I fix it?
Thanks,
Jim Urban

I got the same error.
But then I found out that a pkcs12 file could be used directly as a keystore by jarsigner. So you can skip the keytools step.
I exported my certificate from Netscape Communicator using the Security tool as a .p12 file. Then I pointed jarsigner at my pkcs12 file.
jarsigner -storetype pkcs12 -keystore cert.p12 MyClasses.jar keyname
You can find your keyname alias by entering:
keytool -list -storetype pkcs12 -keystore cert.p12

A few questions about signing JARs for Web start

I'm still a bit new to all this, so just want to clear a few things up.
I'm currently trying to publish an application using Web start, so i know I have to sign all the JARs, as it needs to do some writing to the hard drive.
1. I have my main JAR file, and then two "third party" JAR files in the /lib subfolder, I take it I need to sign those two as well, does it matter that I don't have the .class file for those two, as I didn't write them?
2. I'm running the JARSIGNER program with exactly the same command line apart from the filename of the .jar file, is that correct? or do I need a different certificate for each .jar file?
Just can't seem to get all three signed, Web start says one different one isn't signed each time I try it out.
3. When signing, does it add something to the end of the JAR file itself? as I can't see any extra files created.

Signing adds entries in the mainifest, not in the main file list in the jar file.
You can sign third party jar files, but it is not advisable. An alternative is to put third party jars in a seperate extension jnlp file, if they need all-permissions, you can get the third party jars already signed by whoever supplied them. If not, you do not need to request all-permissions in the extension jnlp file, and that part of the code will be run in the secure sandbox.
/Andy

SSL Cert used to sign Jars for distribution via WebStart

Hi,
I have an SSL cert (Comodo InstallSSL) for my website and wondered if I can use it to sign jars so, when distributed via webstart, the old "untrusted source" message doesn't get displayed. I've been doing a lot of reading but, to be honest, I can't really find my bearings! I have imported the cert into my keystore but get the message when I try to sign a jar:
Certificate chain not found for: myalias myalias must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.I have the following files in relation to my cert:
xxx.cabundle (this can be imported into keytool easily)
cert/xxx.crt (looks like a PGP file, cannot be imported (-import) into keytool)
private/xxx.key
My questions I suppose are:
1. Can I use a cert issued for SSL to sign jars for webstart distribution?
2. If yes to 1; what steps other than importing the cert alone (which generates the message above) do I need to do to achieve this?
Any help would be appreciated!
Rich

Hi,
yes, the pkcs12 certificate includes the private key, as opposed to pb7 which does not.
Sent from Cisco Technical Support Android App

Updating to signed JARs causes problems for older Java versions?

Bear with me on this one -- not a Java developer, but an end user of Java products looking for a little clarification.
We use a product which delivers a Java application via JAR file / web to end users (GlobalScape's EFT server). With the recent release of Java 7 Update 51, users have been running into issues running these JAR files as they are not properly "signed". We're working with the vendor to get updated signed JAR files in place, but they've warned us that these new JAR files will cause errors (or maybe not work at all) on folks who aren't running Java 7 Update 51.
Trying to wrap my head around why that might be. Best theory I can come up with from perusing threads here along with the Java team blogs is that the new security attributes used in the updated JAR files aren't "trusted" by older versions of Java (prior to Update 51?).
We're pushing our vendor for clarification, but curious if someone here could help explain.
Thanks!

I suspect the problem with 'new JAR files will cause errors' is mainly because the vendor keeps enhancing their product, and may not any more support older JREs, or the new jars are no more compatible For example, we build our product on JDK 1.5 ... as some users out there must use that one because the 'newer and better' release does not work for them.
But so far, we have not seen any problems running the 'JRE 7 Compliant' applications on older releases ... provided you can make your application run on latest JRE 7.
In most cases, one can simply remove the previous signature, add (now required) attributes, and sign the same jar again.
But I have yet to find a vendor that would simply add attributes to some older release and re-sign those. Perhaps they can't repeat the build / QA cycle, and would not 'trust' the re-signed jars.
Our curse are signed Cryptographic Provider jars.
Those must be signed by certificates rooted by Sun/Oracle, and adding attributes invalidates that signature - we can re-sign them, but then they won't work. In our case, we are stuck with 5+ year old Bouncy Castle jars, and it does not help us that their 'current' jars are signed with attributes - they are completely incompatible..
IMHO, Oracle failed to think this all thru - or does not care.

I look for guider in signing jars

Hi everybody
for what signing jars is good,for applet jars or desktop applications jars???
and how can I use it? please i need the answerer explanations not url to tutorials
Thanks to every reader to this topic

i need the answerer explanations not url to tutorialsA stupid remark. The tutorials are explanations, and they have already been reviewed, debugged, etc. Why on earth would you prefer someone's random opinion to a properly produced piece of documentation?
At best this is just lazy thinking.

Error when i try to sign .jar for webutil

i have try to use signwebutil.bat in webutil 1.0.6 but i have the follow error_
Generating a self signing certificate for key=webutil2...*
Errore keytool: java.lang.Exception: Non è stata generata la coppia di chiavi, l'alias <webutil2> è già esistente*
+.+
There were warnings or errors while generating a self signing certificate. Please review them.*
+.+
Backing up d:\w\jacob.jar as d:\w\jacob.jar.old...*
+1 file copiati.+
Signing d:\w\jacob.jar using key=webutil2...*
+.+
There were warnings or errors while signing the jar. Please review them.*
Generating a self signing certificate for key=webutil2...*
Errore keytool: java.lang.Exception: Non è stata generata la coppia di chiavi, l'alias <webutil2> è già esistente*
+.+
There were warnings or errors while generating a self signing certificate. Please review them.*
+.+
Backing up d:\w\frmwebutil.jar as d:\w\frmwebutil.jar.old...*
+1 file copiati.+
Signing d:\w\frmwebutil.jar using key=webutil2...*
+.+
There were warnings or errors while signing the jar. Please review them.*

Maybe you could try to change the values in your sign_webutil.bat file:
REM Give your alias key here.
REM
SET JAR_KEY=webutil3
REM
REM Key Password for the given key to be used for signing.
REM
SET JAR_KEY_PASSWORD=webutil3
REM
REM Number of days before this certificate expires
REM
SET VALIDDAYS=360
Francois

Adobe Reader XI, how do I remove the panel on the far right for Tools, Fill & Sign, Comment?

How do I remove this panel on the far right of the screen? It takes up too much space when I move the Adobe window to only the left or right side of my screen. Can it be shrunk like Bookmarks, Attachments and Thumbnails?

Thanks ~graffiti. That got me halfway there. I only want the tool bars on the right to go away. I like the toolbars on the top.
I found if I "Hide Toolbars" and then "Show Toolbars", the Tools Fill & Sign Comment toolbar comes back minimized. The shortcut key is F8. I will have to remember the shortcut so I may rapidly turn off and then show the toolbars.

Algorithms for Signing & Encryption for SAP Java cryptographic Tool kit

Hi,
We want to use SAP Java Cryptographic Toolkit for S/MIME for signing & encryption. Kindly let me know what are all the algorithms it supports for Signing & algorithms it supports for Encryption
With Regards
K.Varadharajan

DES (Data Encryption Standard) algorithm is used to perform the encryption
Policy jurisdiction files regulate which algorithms are available. These jurisdiction files are provided by the same vendor as for your J2SE package.
Regards,
Prateek

Tool for signing jars

Similar Messages

Maybe you are looking for