On 04.11.2014 20:33, Nick Burch wrote:
> Maybe add a catch for it, and log a "your jvm is broken, consider updating" 
> in place of the current failure?
>
> That'd let me roll the 3.11 beta 3 release :)
>

I preferred to add a workaround to use BouncyCastle in this case.
Btw. I usually have the latest JDK 6 as my development/testing jre, so Windows 
seems not to be affected.
I hope the hashing algorithms are not subject to jce policy limitations -
at least I couldn't find something under 
http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProviders.html

Andi.



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to