2 Downloading and Deploying Jipher
Jipher Deployment
Extract the Jipher
JAR file from jipher-10.35.tar.gz. Add
the Jipher JAR file, jipher-jce-10.35-se.jar, to your class
path or your module path. When placed on the module path, it will be observable as the
module com.oracle.jipher.
Note:
The JCA authenticates a security provider by verifying the JAR file's signature at runtime. See Registering the SUN and SunRsaSign Providers for JAR File Signature Verification. Consequently, you cannot extract the contents of the Jipher JAR file and incorporate them into a JAR with dependencies (a JAR file that contains not only a Java application but includes its dependencies) to simplify deployment.At runtime, the native libraries appropriate for the platform on which Jipher is deployed are
automatically extracted from the Jipher JAR file to a
temporary directory. By default, the value of the java.io.tmpdir system
property is used as a parent directory of this temporary directory. Alternatively, you
can specify this parent directory by setting the value of the
jipher.user.dir system property. See Configuring Jipher Through System Properties.
Check the Version of Your Jipher Deployment
The Jipher provider class is com.oracle.jipher.provider.JipherJCE. It contains a main method that prints version information to standard output.
If you run this method and it prints version information without any errors, then the Jipher native libraries have been successfully loaded:
$ java -cp jipher-jce-10.35-se.jar com.oracle.jipher.provider.JipherJCE
JipherJCE Provider 10.35[OpenSSL 3.4.1 11 Feb 2025] (implements AES,
DESede, Diffie-Hellman, DSA, ECDSA, ECDH, HMAC, PBKDF2, RSA, SHA-1,
SHA-2, SHA-3)