File | Date | Author | Commit |
---|---|---|---|
.mvn | 2018-07-07 |
![]() |
[852297] Initial commit (public release) |
bundles | 2021-02-20 |
![]() |
[6cd957] Correct self signed certificate creation ignori... |
releng | 2021-09-25 |
![]() |
[40ef4a] Correct typo in documentation |
tests | 2021-02-20 |
![]() |
[22223c] Update Copyright dates |
.gitignore | 2018-07-07 |
![]() |
[852297] Initial commit (public release) |
.project | 2018-07-07 |
![]() |
[852297] Initial commit (public release) |
COPYING.txt | 2018-07-07 |
![]() |
[852297] Initial commit (public release) |
README.md | 2021-02-20 |
![]() |
[a24a75] Update README |
pom.xml | 2020-02-06 |
![]() |
[696cbc] Bump version to 1.1.0 |
Halimede is a simple to use Certificate Authority. It supports multiple CA (Certificate Authorities)
from a single interface, with each CA is stored within it's own datastore instance.
Halimede supports a large range of public key ciphers, including RSA, DSA, ECDSA (NIST/SEC/ANSI
X9.62/Brainpool Curves), EdDSA (ED25519/ED448), GOST R34.10, DSTU 4145-2002 and numerous Post-Quantum
Ciphers including Rainbow, SPHINCS-256, XMSS/XMSS-MT and qTESLA for X509 Certificate generation.
Halimede is available as either a Standalone Application, as a Plugin for the Eclipse IDE, or
can be integrated with any other Eclipse e4 RCP based application.
Stable downloads are available from https://sourceforge.net/projects/halimede/files/1.1.0-20210220/
Eclipse plugin can be used from within Eclipse via "Install New Software" with
the update site: https://halimede.sourceforge.io/release/1.1.0
Missing Certificate
On installation Eclipse IDE may indicate the Halimede plugins are not signed.
The Halimede plugins are signed using ECDSA NIST P-521 keys/signatures.
However as of writing, Eclipse IDE currently ignores any signatures that are
not RSA based. The signature of the bundles can be verified with
$ jarsigner -verify
from the JDK.
Simply place the plugin jars file into the /dropins or /plugins folder of your Eclipse
installation, and restart Eclipse. Use the Window > CA Manager to open it.
Alternative, use the Install New Software dialog to install from the *.zip p2 bundle.
Run $ mvn clean install
to build. The resulting JAR file is in the target folder.
Deployment artefacts will be located in:
releng/net.sourceforge.dkartaschew.halimede.update/target
and releng/net.sourceforge.dkartaschew.halimede.product/target/products
Note: This project will utilise the required Bouncy Castle Bundles directly
from the local maven repository. If the required JARs are not available, build
errors may occur. To download the required JARs/Dependencies use:
$ mvn dependency:get -DgroupId=org.bouncycastle -DartifactId=bcpkix-jdk15on -Dversion=1.68
This is done, as while Eclipse Orbit has the required bundles, these tend to lag 3+ months behind releases made by The Legion of the Bouncy Castle.