Currently the library provides 2 apps:
com.evolutiongaming.crypto.Decrypt - decrypts all the versions of encryption including legacy onescom.evolutiongaming.crypto.Encrypt - encrypts with the latest version (currently it's V3)
Let's say SREs use the encrypt app and they updated their crypto version first - now it produces V3 cipher-texts only. The apps might upgrade at their own pace and some of them might still be lacking support for V3 decryption. And SREs have no way of producing older versions for specific apps.
This creates tight coupling between SREs internal tools updates and app updates.
I propose to expose in the app possibility to produce legacy versions of encrypted passwords.
With this together we can revamp the apps, probably turning them into 1 with both encryption and decryption modes, for the ease of use.
Currently the library provides 2 apps:
com.evolutiongaming.crypto.Decrypt- decrypts all the versions of encryption including legacy onescom.evolutiongaming.crypto.Encrypt- encrypts with the latest version (currently it's V3)Let's say SREs use the encrypt app and they updated their crypto version first - now it produces V3 cipher-texts only. The apps might upgrade at their own pace and some of them might still be lacking support for V3 decryption. And SREs have no way of producing older versions for specific apps.
This creates tight coupling between SREs internal tools updates and app updates.
I propose to expose in the app possibility to produce legacy versions of encrypted passwords.
With this together we can revamp the apps, probably turning them into 1 with both encryption and decryption modes, for the ease of use.