[v6.0.0] Discussions and proposals

[mCodex]

Since v6.0.0 the lib should use Android's Keystore to encrypt data for better security purposes before saving it into shared preferences.

The problem

Data stored using RNSInfo's versions > 6 was saved in Android's shared preferences without keystore encryption then releasing v6.0 these data could be lost?

On the other hand, data stored using keystore's branch wouldn't be affected by v6

Checklist

• Improve documentation
• Create a branch which merges master and keystore
• Release an alpha version
• Add support for tvOS and MacOS in react-native-sensitive-info.podspec
• Merge everything into master
• Fix macOS build error MacOS build failing #222
• Find a way to automatically migrate data from shared preferences to keystore? (should the library itself handle this?)

[kneza23]

Official RN docs included your library to the Security page https://reactnative.dev/docs/security. It would be amazing if eventually we get Android's Keystore as default storage :)

[mCodex]

@kneza23 thanks for pointing it out! I didn't know 😱 Yeah, I think it is time to do this migration

[mCodex]

This afternoon I will create a new branch from master and I'll merge keystore into that branch. So, we gonna have a starting point for this 👏 👏 👏

--- Edit ---

I've merged everything into feature/keystoreAsDefault.

[mCodex]

There is a new release available in npm which includes keystore by default. For more information, please read here.

[juanapp]

Is there a solution for data migration? I would love to integrate this version but I'm also afraid that it will cause quite some troubles to users that have data saved..

[mCodex]

Is there a solution for data migration? I would love to integrate this version but I'm also afraid that it will cause quite some troubles to users that have data saved..

Unfortunately there is not. Maybe we need an extra method to read from sharedPreferences without using keystore something like getAllUncryptedDataFromSharedPreferences and then every user should handle saving all these infos again using setItem and now everything will be encrypted in Android.

[juanapp]

@mCodex That would be ideal... I think what we need is to have a way to trigger the migration from everything that is stored on SharedPreferences to the KeyStore, keeping the same structure and then deleting it from SharedPreferences. That would save the hassle of the first time run after upgrading.