Well, one of the threads I cited has these various quotes (sic):
"The algorithm of SHA256 is not available with the satadard sun jce
provider.Use Bouncycastle provider.
Configure BouncyCastly then use your usual code."
...
"The SHA-256 algorithm works with my JVM (JDK 1.4.2). A quick google
shows that SHA-256, SHA-384, and SHA-512, were added to the Sun JVM
starting with JDK 1.4.2."
...
"That might be the reason as he is using 1.4.1 version of JDK."
So from my detached perspective, it seems to be a JVM version issue. If
that is true, you could probably assist with a wiki entry instead of a
bug report.
Al
On 4/21/2011 3:45 AM, AlexS wrote:
Peter,
Many thanks for that code snippet, helped me track it down.
My install is 1.4 Viviotech installer and I mode the Jars to put me on
the 1.5 nightly, it seems that if I modify the JRE to use my manually
installed JRE that this works fine so seems to be an issue with the
bundled JRE as part of the installer ?
For anyone else with the issue if using the installer you make such
modifications using regedit and modifying the
HKEY_LOCAL_MACHINE> WOW6432NODE -->Apache Software Foundation --
Procrun 2.0 -->OpenBD-->Parameters-->Java
Should I log the issue on the Open BD tracker as it I guess strictly
speaking it isn't an Open BD issue ?
Thoughts ?
A
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en