KeyStore Explorer Now Open Source
KeyStore Explorer (KSE), in its various guises, is a PKI desktop application project I have worked solo on since 2001. While it started as open source software it has been a closed project for most of the subsequent time. For the last year development has stalled due to a lack of motivation on my part. My concern has been that my lack of activity would lead to the whole project dying.
I am therefore happy to report that KSE is now officially open source software. The new owner Kai Kramer answered my call to arms and has been busy since late July remediating all of the impediments to open sourcing the application, completing the features I had slated for version 4.2 and adding extra functionality. The result is KSE 5.0 which is licensed under GPL Version 3.
The old KSE website http://www.lazgosoftware.com/kse has been decomissioned and now redirects to KSE’s new home at SoureForge http://keystore-explorer.sourceforge.net.
Release notes for 5.0 are available here. Executable downloads for the usual supported platforms are available here. Finally the highlight is the availability, for the first time since 2004, of the source code.
For my own part, I will be stepping back completely from the project to let Kai and the community take KSE forward.
Explore posts in the same categories: KeyStore Explorer, Open Source
Tags: KeyStore Explorer
You can comment below, or link to this permanent URL from your own site.
THE UPWARD SPIRAL 
October 22, 2013 at 9:12 am
That is great news Wayne! I just figured I’d check back to your site and find this post. Very good to hear KSE has a new home, and SF is a good place to be.
Maybe even some of my “pet features” have been implemented 🙂
Best of luck on your future projects.
October 22, 2013 at 9:52 am
Thanks Stian.
If your ideas haven’t been implemented yet then there is a better chance of them happening now that I’m not in the way 🙂
November 13, 2013 at 3:00 pm
The main reason why i decided to test drive that tool was because other GUI tools seems to lack support for SAN (Subject Alternative Name) management.
So far, i was able to add that SAN certificate extention during the process of creating a new certificate.. But the CSR will lost track of this SAN extention.. So currently there’s no way i could make use of this SAN feature with certificate signed with CA’s.
Look to be bug !
Is that SAN feature ever tested with CSR’s ?
Beside that its very good !
November 13, 2013 at 4:46 pm
It’s not a bug. CSRs don’t persist v3 extensions from certificates. To include an extension in a signed certificate the signing CA must include it in the CA Reply. KSE supports this.
November 13, 2013 at 9:42 am
Hi, I found a bug in the application when you import a certificate. The first certificate you import is ok, with the next ones the app keep using the path of the first imported certificate. COuld you check that out? Using KSE last version.
Cheers!
AR
ps : great tool!
November 13, 2013 at 10:54 am
Arnaud,
Go to http://keystore-explorer.sourceforge.net and log the issue. The new maintainer will be able to help you from there.
December 25, 2013 at 4:14 pm
Hi Wayne Grant, do you can help me?
i have keystore which was created from android AIDE. this key has 2 Entry keys this same name but in other case (moscowcrafterpk and MoscowCrafterPK). Any way to delete or rename one entry? i try your software but if i try to rename or delete one key, then second key get error..
ps sorry for my bad english.
if you need i can send you my key.
December 25, 2013 at 4:21 pm
I don’t support KSE anymore. See http://keystore-explorer.sourceforge.net where you can log an issue.