Be the first to post a text review of StrongKey. Rate and review a project by clicking thumbs up or thumbs down in the right column.

View all reviews

• Release Candidate 1.4 now available

  StrongAuth, Inc.'s StrongKey Symmetric Key Management System software ---------------------------------------- Release Candidate 1.4 - April 16, 2009 ----------------------------------------- This release implements a two new features. These are: 1) It is now possible to use a different password for the private-keys of digital certificates in JKS keystores, from the password of the keystore itself. In previous releases, StrongKey assumes that the password of the JKS keystore and all cryptographic keys inside the keystore were identical. Now, they can be separated. Use of this feature requires changing the following properties: 'symkey.skcl.config.jceprovider.skcl.keystore.samepasswordforcert' 'symkey.skcl.config.jceprovider.xwss.keystore.samepasswordforcert' 'symkey.sks.config.jceprovider.sks.keystore.samepasswordforcert' 'symkey.sks.config.jceprovider.xwss.keystore.samepasswordforcert' 'symkey.skcl.config.jceprovider.skcl.certificateDNPassword' 'symkey.skcl.config.jceprovider.xwss.certificateDNPassword' 'symkey.sks.config.jceprovider.sks.certificateDNPassword' 'symkey.sks.config.jceprovider.xwss.certificateDNPassword' The default value for all '*samepasswordforcert' properties is 'true', indicating that the password for the keystore and the appropriate private-key is the same (note that the XWSS entries are used by the underlying WSS layer for message-level security, while the non-XWSS entries are used by StrongKey directly. It is possible to have unique keys/certificates for each of these 4 entries, unlike the samples included in StrongKey that share keys/certificates between XWSS and StrongKey). To use a different password for the XWSS private-key on the client, change the setting from 'true' to 'false for the propertye: 'symkey.skcl.config.jceprovider.xwss.keystore.samepasswordforcert' and set the new private-key password for the property entry: 'symkey.skcl.config.jceprovider.xwss.certificateDNPassword'. It is necessary to restart the server at that point so that the software reloads the new values. 2) The xenc utility implements key-rotation and shows how this is accomplished using StrongKey. The source code for xenc shows key- rotation for file, directories and for database-columns. StrongKey can rotate keys while the primary application continues to run. BUG-ID DESCRIPTION ------ ---------------------------------------------------------- 3 Printing of keystore password in logs The SecurityEnvironmentHandler.java had a logging entry tha was printing the password to the JKS keystore after acquiring it. This entry has now been suppressed. SHA1 Message-digests -------------------- 5bab33eff560d73ebfe90400abaa38170c3323dc strongkey-rc1.4-build-208.zip 96a6ee2d1dd5ad7af0d9196f91781d2490d6f194 strongkey-src-rc1.4-build-208.zip SHA256 Message-digests ---------------------- e2222f49717dfa8f9115707eec2849259b86540f4ebd6a84075fe204efdb5f4d strongkey-rc1.4-build-208.zip 8ad6e045a2f78ee663644e97cc5a155d5a7f87805433942fe74e1f179095e8b0 strongkey-src-rc1.4-build-208.zip

  posted by arshadnoor 206 days ago

• File released: /StrongKey/Release Candidate 1.4/strongkey-src-rc1.4-build-208.zip

  posted 206 days ago

• File released: /StrongKey/Release Candidate 1.4/strongkey-rc1.4-build-208.zip

  posted 206 days ago

• StrongKey Release Candidate 1.4 file released: strongkey-src-rc1.4-build-208.zip

  posted 206 days ago

• StrongKey Release Candidate 1.4 file released: strongkey-rc1.4-build-208.zip

  posted 206 days ago

• SKSML is now an OASIS Committee Specification

  The Symmetric Key Services Markup Language (SKSML), originally created by StrongAuth, Inc., has been voted as an OASIS Committee Specification. Read more: http://www.strongkey.org/index.php.

  posted by arshadnoor 276 days ago

• Release Candidate 1.3 available

  StrongAuth, Inc.'s StrongKey Symmetric Key Management System software ---------------------------------------- Release Candidate 1.3 - February 05, 2009 ----------------------------------------- This is a minor release to fix the bug identified below. A hard-coded date in cli.jar prevented the sample data from loading correctly after January 01, 2009. This has now been fixed. Additionally, when Sun fixed the JDK to take care of a bug in the JCE related to 3DES key-sizes, we updated our code to fix our workaround. NOTE: This release has been tested with JDK1.5.0_15. It does NOT work with JDK 1.5.0_17 since the Sun Application server does not work with the 1.5.0_17 release of JDK. NOTE: If you're having trouble installing JWSDP 2.0, you'll find the answer here: http://forums.sun.com/thread.jspa?threadID=527889&start=10&tstart=345 BUG-IDDESCRIPTION ---------------------------------------------------------------- 2Failure to update KeyUsePolicy #5 When cli.jar is run to load the sample XML data, it fails to update KUP #5 since the hard-coded date in cli.jar was set to Dec 31, 2008. After January 01, 2009, this program failed to update the KUP. This has been fixed. While we reset the hard-coded date to December 31, 2010, we hope to release a better model for loading sample data in the next release of StrongKey.

  posted by arshadnoor 276 days ago

• File released: /StrongKey/Release Candidate 1.3/strongkey-src-rc1.3-build-208.zip

  posted 276 days ago

• File released: /StrongKey/Release Candidate 1.3/strongkey-rc1.3-build-208.zip

  posted 276 days ago

• StrongKey Release Candidate 1.3 file released: strongkey-rc1.3-build-208.zip

  posted 276 days ago