Java standard crypto API vs. specific provider (Bouncy Castle)

685 views Asked by At

I'm developing a java application that uses some basic/common crypto (AES, 3DES, DH, ECDH) and is supposed to run on as many platforms (mainly Win/Linux/Android) as possible. Concerning the crypto part I thought it would be best to use the standard Java API so users can use whatever cryptographic provider they desire.

Luckily/Unfortunately I inherited some old code fixed to Bouncy Castle. Now I have to decide between either giving up my idea of staying independent of any crypto provider or updating/rewriting the old code to work with the standard API. The amount of work for updating/rewriting would be feasible but is it worth the while?

0

There are 0 answers