Local_policy.jar Download

3. Copy the local_policy.jar and US_export_policy.jar files extracted in the previous step to the lib\security directory of your JRE making sure to backup previous versions of these jar files should you decide to revert back to the previous installation.

3. Copy the local_policy.jar and US_export_policy.jar files extracted in the previous step to the lib/security directory of your JRE making sure to backup previous versions of these jar files should you decide to revert back to the previous installation.

Download 🔥 https://tinurll.com/2y5Iii 🔥

Each JRE installation contains two jar files: local_policy.jar and US_export_policy.jar. To enable FIPS mode for an SM component, you need to replace these two jar files with the unlimited strength policy files. To be more specific, you need to do this for the JRE instances used by the following Service Manager (SM) components:

To use unlimited jurisdiction policy files by default, place the US_export_policy.jar and the local_policy.jar in the jre/lib/security/ directory of your JRE. Visit the Oracle website to download the unlimited strength JCE policy files:

To use the included 256-bit encryption algorithms within Java, Oracle Java JDK or JRE requires you to download and replace the US_export_policy.jar and local_policy.jar files under your $JAVA_HOME/jre/lib/security/ directory with a variant of these files called JCE Unlimited Strength Jurisdiction Policy Files obtained here.

Installation Instructions Download JCE 1.2.1. You can save the downloaded file anywhere on your local disk.Note that JCE 1.2.1 requires that you haveJavaTM 2 SDK v 1.2.1 or later or JavaTM 2 Runtime Environment v 1.2.1 or later already installed.Uncompress and extract the downloaded file. This will create a directory named jce1.2.1, with two subdirectories nameddoc and lib.The JCE 1.2.1 framework and the "SunJCE" provider are supplied as extensions (also known as "optional packages") to the Java 2 platform. The lib subdirectory extracted in the previous stepcontains the jce1_2_1.jar and sunjce_provider.jar files. The lib subdirectory should also contain JAR files for jurisdictionpolicy files: US_export_policy.jar and local_policy.jar. Two types of installations are supported, described below.In both cases, the jurisdiction policy files must be installed inthe same directory as that which contains the JCE 1.2.1 framework JAR file. In some cases, permissions must be granted to the JCE 1.2.1 framework and/orthe "SunJCE" provider for when applets or applications using JCE are run while a security manager is installed. Note: There is typically a security manager installed whenever an applet is running, and a security manager may be installed for an application either via code in the application itself or via a command-line argument.Installation Option 1: The JCE 1.2.1 framework is an "installed" extension. Providers are installed or bundled. (Note: A package (or packages) housed in a JAR fileis considered "installed" if the JAR file is stored in a particulardirectory established for all installed extensions, as described below.) Pro: This is the most convenient type of installation.Permissions do not need to be granted to installed extensions,since the default system policy filegrants all permissions to installed extensions. Con: You must have access rights that allow you towrite to the special directory that holds installed extensions. Instructions: To make the JCE 1.2.1 framework an installedextension, move or copy the jce1_2_1.jar, US_export_policy.jar, and local_policy.jar files from the lib subdirectory extracted in the previous step tothe standard place for the JAR files of an installed extension:\lib\ext [Win32]/lib/ext [Solaris] Here refers to the directory where the runtime software is installed, which is the top-level directory of the JRE or the jre directory in the JavaTM 2 SDK software. For example, if you have J2SDK v 1.2.2 installed on Solaris in a directory named jdk1.2.2, youneed to install the JAR files in the following directory:jdk1.2.2/jre/lib/ext Similarly, if you have JavaTM 2 Runtime Environment v 1.2.2 installed on Solaris in a directory named jre1.2.2,you need to install the JAR files in the following directory:jre1.2.2/lib/ext To also make the "SunJCE" provider an "installed" extension,move or copy sunjce_provider.jar to that same directoryfor installed extensions. If you want to make the "SunJCE" provider a "bundled" extension, see Bundled Extensions. Permissions: You will need to grant the "SunJCE" provider the permissions listed belowif it is bundled and if a security manager is installed. You don't have to understand what the permissions mean, but you must grant them, for example, in a policy file, or the "SunJCE" provider won't work.Here are the permissions that must be granted: java.io.FilePermission to read the jce1_2_1.jar file java.lang.RuntimePermission to get class protection domains java.security.SecurityPermission to put (set) provider properties. A sample statement granting these permissions appearsbelow. Such a statement could appear in a policy file. In this example, theJCE 1.2.1 framework is assumed to be an installed extensionand the sunjce_provider.jar file is assumedto be in the /work directory. grant codeBase "file:/work/sunjce_provider.jar" { permission java.io.FilePermission "/jdk1.2.2/jre/lib/ext/jce1_2_1.jar", "read"; permission java.lang.RuntimePermission "getProtectionDomain"; permission java.security.SecurityPermission "putProviderProperty.SunJCE"; }; Once you have completed this type of installation, go on to thenext step to register the "SunJCE"provider.Installation Option 2: The JCE 1.2.1 framework andJCE providers are located on the class path (not installed extensions). Pro: The JCE 1.2.1 framework and providers don't have tobe put in a special directory. This is very useful if you share a Java 2 installation with other people and you don't have access rightsallowing you to write to the directory for installed extensions. Con: Permissions need to be granted to the JCE 1.2.1 frameworkand JCE providers for when applets or applications using JCE are run while a security manager is installed. Instructions: Move or copy the JCE 1.2.1 framework file jce1_2_1.jar and jurisdiction policy files (US_export_policy.jar, and local_policy.jar)to a directory that will be listed on your class path.(Note: All these files must be in the same directory.)Move or copy the "SunJCE" provider file sunjce_provider.jarto another directory that will be listed on your class path. It canbe the same as the directory containing the JCE 1.2.1 framework, ora different directory. Be sure to set the class path to include the directoriescontaining the JCE 1.2.1 framework and "SunJCE" provider JAR files. Permissions: The following permission should be granted to the JCE 1.2.1 framework when a security manager is installed:java.security.AllPermissionBelow is a sample statement granting this permission.Such a statement could appearin a policy file. In this example, theJCE 1.2.1 framework is assumed to be in the/home/mydir directory. grant codeBase "file:/home/mydir/jce1_2_1.jar" { permission java.security.AllPermission; }; The following permissions should be granted to the "SunJCE"provider (and other JCE providers) when a security manager is installed:: java.io.FilePermission to read the jce1_2_1.jar file java.lang.RuntimePermission to get class protection domains java.security.SecurityPermission to put (set) provider properties. A sample grant statement granting these permissions appearsbelow. In this example, theJCE 1.2.1 framework is assumed to be in the/home/mydir directoryand the sunjce_provider.jar file is assumedto be in the /work directory. grant codeBase "file:/work/sunjce_provider.jar" { permission java.io.FilePermission "/home/mydir/jce1_2_1.jar", "read"; permission java.lang.RuntimePermission "getProtectionDomain"; permission java.security.SecurityPermission "putProviderProperty.SunJCE"; };Register the "SunJCE" provider. Although the "SunJCE" provideris supplied with every JCE 1.2.1 installation, it still needs to beconfigured explicitly, either statically or dynamically, before itsservices can be accessed:Static registration of SunJCE provider Add the "SunJCE" provider to your list of approved providers. Thisis done statically by editing the security properties file [Win32] \lib\security\java.security [Solaris] /lib/security/java.securityHere, as in the previous step, refers to the directory where the JREwas installed. For example, if you have J2SDK v 1.2.2 installed on Solaris in a directory named jdk1.2.2, youneed to edit the following file:jdk1.2.2/jre/lib/security/java.securitySimilarly, if you have JavaTM 2 Runtime Environment v 1.2.2 installed on Solaris in a directory named jre1.2.2,you need to edit this file:jre1.2.2/lib/security/java.security One of the types of properties you can set in java.securityis of the following form: security.provider.n=providerClassName The java.security file should have a statement of that form for each provider to be registered statically.Each such statement declares a provider, and specifies its preference ordern. The preference order is the order in which providers aresearched for requested algorithms (when no specific provider is requested). The order is 1-based; 1 is the most preferred, followedby 2, and so on.J2SE comes standard with a provider named "SUN", which isautomatically configured as a static provider, as follows: security.provider.1=sun.security.provider.Sun To configure other providers, follow this line with other lines of the proper format, replacingproviderClassName with thefully qualified "master class name" you obtainfrom the provider vendor,and substituting n with the priority that you would like toassign to the provider. For example, if you would like to configure "SunJCE" asyour second preferred provider, add the following line to thejava.security file after the line for the "Sun" provider: security.provider.2=com.sun.crypto.provider.SunJCEDynamic registration of SunJCE provider To dynamically register the SunJCE provider (instead ofstatically), add the following lines of code at the beginning of your program: Security.addProvider( new com.sun.crypto.provider.SunJCE()); This type of registration is not persistent. 17dc91bb1f