You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you recommend something to migrate user data previously encrypted using AES-CBC in keychain/keystore (now deprecated and considered as a vulnerability by my security team) to AES-GCM ?
That would be nice if this library explained how to manage the algorithm transition without data loss.
The text was updated successfully, but these errors were encountered:
Hey @Aure77
The storage type is only needed for setGenericPassword, while getGenericPassword uses the cipher that was originally used to store the credentials, ensuring backward compatibility. You can implement your own migration logic: use getGenericPassword and if the cipher storage is AES_CBC, resave it with AES_GCM_NO_AUTH.
Would you prefer having an automatic upgrade logic built into the library?
Did you recommend something to migrate user data previously encrypted using AES-CBC in keychain/keystore (now deprecated and considered as a vulnerability by my security team) to AES-GCM ?
That would be nice if this library explained how to manage the algorithm transition without data loss.
The text was updated successfully, but these errors were encountered: