On Thu, 19 Feb 2015, Andreas Beeker wrote:
P.S. BTW why using bcprov when today built-in into JDK javax.crypto
package gives everything (in imho better shape and performance)
out-of-the-box including AES256?
the compile-lib is for additional libraries which are used for features
like xml signatures or additional encryption settings, just have a look
CipherAlgorithm or HashAlgorithm to see which algorithm are not
supported ... and of course we are based on JDK 6, so newer
implementations can't be taken into account
At some point (though not yet!), we'll find some reason why we need to
bump the minimum JDK version up to 7. While the signature stuff is fresh
in mind, is it worth raising a bug in bugzilla and noting down what'd be
involved in swapping from bouncy castle to javax.crypto when we do? That
way, as and when we have the need to move to a newer JDK/JVM, we've notes
on how to reduce dependencies when we do!
Thanks
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
