leonardoxh / keystore-ultimate Goto Github PK

Improve documentation on encrypt and decrypt methods

Can I save password in phone storage using keystore.when app is deleted and reinstall again , i want get password from phone storage.i dont want using sql lite,preference. which are dependent on app storage.

Hi, I am a graphic designer, I want to help others in graphic design.

After I review your project, you have no logo on this project yet. Therefore I want to contribute to this project by creating a new logo / icons and It's free. Do you want it?

Current implementation is using class name (CipherPreferencesStorage) as part of shared preferences name (holding the encrypted data). This won't work if Proguard/obfuscation is used in project; classname of CipherPreferencesStorage will be scrambled by obfuscator (unless exclusion rule is added), and shared prefs name could vary per build - resulting in loss of data between builds.

1. Build app without obfuscation, data is available via com.github.leonardoxh.keystore.store.CipherPreferencesStorage_security_storage.xml shared pref
2. Recompile same app with obfucation, data is available via ab.c.d_security_storage.xml shared pref
3. Modify deps, recompile same app with obfucation, data is available via ab.c.e.d_security_storage.xml shared pref

= implementation should not use classname in shared pref name as it will not remain consistant between builds if obfuscation is used

Should I abstract the "data source" so in this way we can save the encoded value in SQLite for example?

When I use the library on Api 22, the method call:

cipherStorage.encrypt(alias, data)

return the following message:

"Can´t generate certificate" with the following detailMessage:
"private exponent cannot be extracted"

Right now I override the CipherStorageFactory for test artefact and the main artefact, but this causes some problems running the unit tests from command line, also it causes some confusions on class path.

I need create another main artefact that depends on the library artefact to solve this problem.

I am inclined to think this library works with API 16.