SEAL 1.4+
Export Policy
JDK 1.4 and 5.0 are shipped with policy files that support strong but not unbounded encryption strength. However, SUN and IBM do distribute policy files that allows unbounded encryption strength which is needed by the SOSI component:
- Download og extract US_export_policy.jar and local_policy.jar from
- Copy these two files to $JRE_HOME/lib/security and overwrite the existing files.
JCE Providers are now handled via properties in Seal. Hence there is no need to edit java.security, etc.
SEAL 1.0 - 1.3
Export Policy
JDK 1.4 is shipped with policy files that supports strong but not unbounded encryption strength. However,
SUN does distribute policy files that allows unbounded encryption strength which is needed by the SOSI component:
- Download og extract US_export_policy.jar and local_policy.jar from
- Copy these two files to $JRE_HOME/lib/security and overwrite the existing files.
Configuring JCE with support for RSA
The OCES certificates uses SHA-1 secure hashing with RSA encryption based on 1024 bit keys. This combination of security
is not supported by Sun's JCE provider implementation. Therefore you need to configure your JDK as follows:
Bouncycastle Provider
Legions of the Bouncy Castle offer an Open Source JCE Provider that is widely used in projects outside of USA.
To install the provider you need to do the following:
- Get bcprov-jdk14-132.jar from http://www.bouncycastle.org/download/bcprov-jdk14-132.jar.
- Copy bcprov-jdk14-132.jar to $JRE_HOME/lib/ext (note: on windows JRE_HOME is %JAVA_HOME%/jre)
- Open $JRE_HOME/lib/security/java.security i a text editor
- Add security.provider.[number]=org.bouncycastle.jce.provider.BouncyCastleProvider to the list of providers. On a SUN JRE, the bouncycastle provider must be placed right after the sun.security.provider.Sun provider. Rename all subsequent providers accordingly (i.e. ''security.provider.2'' to ''security.provider.3'' etc.)