Since Java 9, AES ciphers with unlimited strength are available by default.
When Aspose Cells is running on Java 9, it could delegate to these built-in cipher suites when performing AES encryption/decryption, and only fall back to BouncyCastle as a second option.
In addition, perhaps it would be a good idea to include a repackaged version of bouncycastle (using the Maven shade plugin, or similar).
That way, Aspose Cells for Java users don’t need to handle an additional external library dependency, and the potential version conflicts, in case their own code or project dependencies use a different BouncyCastle release.
@TarasTielkes,
Thank you for your query. We have reviewed your requirement but we need to look into it more. We have logged the issue in our database for investigation and for a fix(if possible). Once, we will have some news for you, we will update you in this topic.
This issue has been logged as
CELLSJAVA-42947 - Need for BouncyCastle on Java 9 and above
@TarasTielkes,
For older versions prior to 19.4, it is possible that the built-in cipher suits will be used instead of BouncyCastle even though you might prefer by adding the library of BouncyCastle. But in recent versions, we have changed the logic and if BouncyCastle’s library is accessible then we will use it instead of the built-in cipher suits.
You may try our latest fix/version to check whether this issue has been solved. If not, please provide the details so we can reproduce the issue and try to solve it.
Aspose_Cells_Java_v19.6.2.zip (6.5 MB)