Prototype of Google Drive Integration with KeePassDroid #41
Conversation
This file contains 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
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.
I was working on a prototype of KeePassDroid with Google Drive Integration and wanted to send the pull request once it was working. The changes to the code in KeePassDroid are minor but the real issue to solve is how to avoid adding the 3 new permissions to KeePassDroid for Google Drive and the authentication APIs. It might be possible to create a shim Android app that has the extra permissions and then communicate with that app via intents from KeePassDroid to avoid introducing the new permissions. Anyway, just wanted to upload my project once it was working.