KeyStore Explorer is an GPLv3 open source project. The source code (and documentation) is maintained on GitHub. While most of the work was done by Wayne Grant and Kai Kramer, there have been also many user contributions to the project.
To make it easier for users who would like to get involved and help us improve KSE, this section contains suggestions and guidelines on how to contribute.
One of the best ways you can help us improve KSE is to let us know about any problems you find with it.
The KSE project uses GitHub issues to report and track issues.
Before you file an issue, search for it to see if anyone has already reported it. If you find your issue, check if you can provide additional information, that might be useful to resolve the issue.
If no one has reported your bug, file the bug. Please describe the problem in detail. Be sure to include:
- Steps to reproduce the problem.
- What happened.
- What you think the correct behavior should be.
- Don't forget to mention which operating system and which version of Java and KSE you're using.
In general, put as much information in bugs as you can. The more detail you provide, the more likely your issue is to be resolved.
Important: Please be on the lookout for any follow-up questions we may have.
If you want to contribute to the code, go to GitHub, fork the KSE repository, apply your changes and open a pull request (PR). GitHub provides detailed information on the process on their website:
The Ant script contains instructions on how to build KSE.
In order to make the review of the PR a pleasant experience for contributors and reviewers and to preserve the quality of the code base, it is important to:
- Make sure the code changes are well tested and that they cause no unwanted side effects.
- Verify that all existing and new tests pass.
- Check that the code formatting matches the existing code.
- Make sure no unrelated or unnecessary reformatting changes are included.
If you intend to implement a non-trivial enhancement or a new feature, please make sure there is a issue that corresponds to your contribution – either created by you or by somebody else. Announce in the issue that you intend to work on it to make sure that the work is not done twice. This is also a good way to get some guidance on how to beste tackle a problem or discuss implementation ideas. It is also necessary to sign a Contributor License Agreement (CLA) in this case.
Good documentation is crucial for any kind of software. You can help improving the documentation:
- Please report missing, incorrect, or out-dated documentation as an issue.
- Please open an issue if you think the website could be improved.
You are welcome to translate the KSE application or documentation into your own language. Just create a issue where you announce that you want to work on translating KSE in a certain language.
If you like KSE, why not recommend it to your friends, colleagues or blog followers? Mention it in your blog, on twitter, in forums, on StackOverflow...
We would like to thank all contributors for their commitment and support.
Those who contributed code, documentation or translations are listed by name below.
|David Harper||5.1.1||Fixed Linux start script, it works now if called from outside the KSE folder.|
|Uri Blumenthal||5.1.1||Fixed import of EC keys.|
|Chris Kistner||5.2||Support viewing of non-CRT RSA private key fields.|
|Chris Ridd||5.2||Added IPv6 addresses for SubjAltName extension.|
|Davy Defaud||5.2||Added RPM packaging for Mageia.|
|Kevin Herron||5.2||Installing the JCE Unlimited Crypto Strength policy is no longer necessary.|
|Uri Blumenthal||5.2||Added several ExtendedKeyUsage (AdobePDFSigning, ...) types.|
|Filip Jirsák||5.2||Fixed AuthorityKeyIdentifier extension.|
|Josef Ludvicek||5.2.1||Fixed a problem with kse.sh when it's executed through a symlink.|
|Peter Breur||5.2.2||Fixed authorityCertIssuer in AKI extension.|
|Andreas Schwier||5.2.2||Ignoring unsupported certificate types now.|
|Andreas Schwier||5.2.2||Fixed problem when generating EC keys with crypto devices.|