Fix android security api suggestions#42
Open
fat-fellow wants to merge 1 commit intoweeeBox:masterfrom
Open
Conversation
fat-fellow
force-pushed
the
fix-android-security-api-suggestions
branch
2 times, most recently
from
f96ed2c to
d307ba8
Compare
fat-fellow
force-pushed
the
fix-android-security-api-suggestions
branch
from
d307ba8 to
3cc135e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://developer.android.com/jetpack/androidx/releases/security
https://developer.android.com/reference/androidx/security/crypto/EncryptedSharedPreferences
These libraries have been discontinued for quite some time, so I believe the documentation should be updated to reflect the current state of the ecosystem.
As far as I understand, Google’s current guidance is to rely on the Android Keystore for secure key management, while leaving the choice of encryption mechanisms to developers. In practice, this means storing cryptographic keys in the Keystore and using them with a cipher of choice to encrypt application data on top of the file-based encryption already provided by the OS.
It would be helpful to clarify this approach in the recommendations to avoid confusion and ensure developers follow modern security practices.