Unpacking the Source Code Running the Program SecurityTool Class Keystore Class Create Key and Get Certificate Creating a Self Signed X.509 Certificate Create a Client and Server Pair of Keystores Caveats

tecreations-security-*-<provider>-*.jar

 

 

Unpacking the source code.

WinRar can open and extract .jar files. I recommend to use it to extract your projects.

The operator would typically open the .jar in WinRar, and then output to whatever location they would prefer. The tecreations packages use the Documents folder to store project data directories. On Windows, <java:USER_HOME>\Documents\<tec:ProjectDir>\.

On Mac and Linux, this would be <java:USER_HOME>/Documents/<tec:ProjectDir>/.

 

 

Running the Program

In a terminal window, java -jar signed-tecreations-security-1.0-BC1.69.jar in the directory you downloaded to should cause the ca.tecreations.launcher.Launcher class to operate the jar. You must select ca.tecreations.security.apps.SecurityToolApp and then click "Launch". The program will run or you don't have a suitable Java Runtime Environment.

 

 

SecurityTool Utility Class

ca.tecreations.security.SecurityTool

The SecurityTool class embodies the attributes and functionality associated with a user's probable needs for tecreations software. Note there are two classes named SecurityTool, the tool itself and the application. ca.tecreations.security.SecurityTool is a convenience class to facilitate high-level programming.

The majority of the useful functionality is exposed as menu commands within the ca.tecreations.security.apps.SecurityTool application.

 

 

Keystore Class

ca.tecreations.security.Keystore

The Keystore class embodies the attributes and functionality associated with a Java KeyStore object. Note the difference in spelling. It is a convenience class to facilitate high-level programming.

The majority of the useful functionality is exposed as menu commands within the SecurityTool application, therefore for example usage of the code, refer to the following classes: 

    ca.tecreations.security.Keystore,
    ca.tecreations.security.SecurityTool,
    ca.tecreations.security.apps.SecurityTool

The user must specify the Certifying Authority before submitting a CSR request to validate the certificate response before attempting to store said certificate.

 

 

Create Key and Get Certificate

This flow allows the programmer open a Keystore object, create a key, a certificate signing request (CSR) and certificate response from a Certifying Authority.

 

 

Creating a Self-Signed X.509 Certificate

The SecurityTool.getSelfSigned(...) method allows the programmer to create a self-signed X.509 certificate.

 

 

Create a Client and Server Pair of Keystores

This flow allows the programmer to create a self-signed pair of keystores, each containing their own key and self-signed certificate of other party.

Good enough for security, but, #WORLDWIDE., ...

 

 

Caveats

I've tried my best to keep the reference to the topic with the relevant code. The listed source is what I've built to test the correct functionality for the task. The .jars in /jars/ have worked for Bouncy Castle version 1.69. There was no integrity checks done and as such, should not be relied upon. If I recall, ca.tecreations.pomdeps.DependencyViewer does do the integrity checks, however, as always, you should ensure your code and dependencies are trusted. For DependencyViewer, specify a valid POM file and include your dependencies in the <dependencies> section, save POM text or reload, and commit to target.

Stores in /temp/