For more security, can you change old spongycastle (based on old bouncycastle) to bouncycastle?
Hmmm... this is a hard one.
We chose to use spongycastle since we need to use updated BouncyCastle for updated crypto code not available from stock BouncyCastle, which versions differ with different Android versions.
Happy to know if there is a way to use updated BouncyCastle without letting Android apps ignore the version we want to use, but always fall back to Android's own BouncyCastle.
@TranceLove: Thanks for your comment!
Currently Bouncy Castle last version is 1.65 and Spongy Castle last version is 1.58.
Spongy Castle is a fork of Bouncy Castle.
Please look previous links :)
Since several years, a lot of projects have already moved from Spongy Castle to Bouncy Castle because the project is dead.
You can see discussion "34" in https://github.com/rtyley/spongycastle/issues.
Thanks @Neustradamus, @rtyley/spongycastle#34 and a quick Google/StackOverflow both pointed to a node.js module to help building bouncycastle at their own namespace: @jbuhacoff/nodejs-mybc-util
Let's see when I have time to make our own bouncycastle jars.
@TranceLove: nodejs-mybc-util is optional because a lot of projects have been migrated without...
@TranceLove: Not possible to add directly in gradle?
@TranceLove: Not possible to add directly in gradle?
Sorry for overlooking - that the discussion mentioned above actually pointed out that there is no namespace collision since Android 3.0.
I then tried a bit, seems promising. But is getting Espresso test failures on Kitkat - seems not directly related to migration to BouncyCastle though coding problem actually, otherwise is fine.
Will retract #1874 after tests passed using changeset from #1831.
Great, thanks for looking into this @TranceLove
@TranceLove, @VishalNehra, @bowiechen: Thanks a lot!
But not complete: https://github.com/TeamAmaze/AmazeFileManager/search?q=spongycastle&unscoped_q=spongycastle