Add support for SmartCard-HSM about keystore-explorer HOT 8 CLOSED

That's some interesting news. So, the provider is GPL licensed but only available for your customers that bought SmartCard-HSM?

from keystore-explorer.

The provider jar is distributed as part of the Smart Card Shell in the OpenSCDP Project. The Smart Card Shell is the primary tool to work with a SmartCard-HSM. It's free to download.

We share source code with our customers via the CardContact Developer Network, which is a free service for which you need a SmartCard-HSM to get access. So yes, you need to have a SmartCard-HSM to get access to the CDN Redmine and Git repositories. It's pretty much "use what you sell": Getting access to the CDN is the first thing you should try with a new SmartCard-HSM to get yourself acquainted. You will receive a X.509 certificate from the DevNet-CA with an automated registration process and use that for TLS-Client Authentication in the browser. At the same time you use the key to get SSH access to the Git repos.

from keystore-explorer.

Okay, I see.

I am fine with adding direct support for SmartCard-HSM in KSE. My only condition is that the provider jar is optional for compilation of KSE (like darkula) and also at runtime. If the provider is not available at runtime, the menu item for opening SmartCard-HSM shouldn't be displayed (like MSCAPI under Linux/Mac OS).

from keystore-explorer.

That can be done.

But it's also no problem to include the provider jar in the source repo and make it easier for users to get it running. Without the jar included, I will probably create a separate distribution as part of the SmartCard-HSM Starterkit.

Please let me know by PM if you like to get some samples for testing ([email protected]).

from keystore-explorer.

I would prefer if you create a separate distribution as part of the starter kit. There are several reasons for this. First of all only a very small percentage of KSE users are also SmartCard-HSM users. Then, I will soon switch to gradle and remove as many jars from the KSE repository as possible. Also, the maintainers of the linux distributions seem to have a problem with Java libraries that are not part of the distribution (for whatever reason).

from keystore-explorer.

Fair enough. Btw. we changed to ant+ivy, because that allows to keep the flexibility of ant and still have a nice dependency management.

from keystore-explorer.

I've changed the code to enable SmartCard-HSM support only if the class SmartCardHSMProvider is found in the classpath.

Unfortunately kse does not automatically add jar files placed in the lib directory to the classpath. I also don't want to encourage users to mess with jre/lib/ext.

One workaround I found is to add smartcard-hsm-provider.jar in the manifest for kse.jar. That way the provider is included if its present in the lib directory. Without the jar, the additional element in the classpath is ignored.

from keystore-explorer.

Yes, sounds fine.

from keystore-explorer.