-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autofill and additional features #77
Conversation
binsky08
commented
Feb 26, 2021
•
edited
Loading
edited
- Mark compromised credentials
- Add URL copy and open button
- Add app start password option based on the android user authentication (partly solves Password master on open app #67)
- Enable code optimization in the C compiler options to speed up the C based encryption
- Use a random number generator for the salt length
- Do not reload the whole vault after adding, editing or deleting a credential
- Move double RequestParams generation logic of Credential.java to an own function
- Remove Java bouncycastle crypto library
- Implement Android autofill feature (requires at least Android API level 26)
- based on the work of https://github.com/HahUK/passman-android/tree/feature-android-autofill-and-gen-additions
- solves Android Oreo Autofill #50 (autofill issue)
- autofill "automatic mode" requires the app to run in the background with unlocked vault, uses the opened vault
- "offline mode" saves a selected vault offline (encrypted), but requires a saved vault password to run completely independently in the background
- hopefully fixed bug with unset compromised field
- remove debugAndToast functions from generalUtils
- add custom response handlers
New menu options added: 1.) Lock Vaults - lock all unlocked vaults 2.) Clear Saved Vault Creds - remove saved vault creds 3.) Enable Autofill - Helps user enable the autofill service UI now shows loading screen whilst loading in Vaults from the API.
Looking to handle more fields and applications.
Looking to handle more fields and applications. Addition of notification which can copy the credential entry to the clipboard. Notification fires on Credential long click.
Fix bogus? API responses from POST and PATCH to credentials endpoint
Improvements to Notification handling. Cody Tidy Up
…utofill-and-gen-additions
…github.com/hahuk/passman-android into feature-android-autofill-and-gen-additions
…hub.com/hahuk/passman-android into feature-credential-display-autoLink-url
…github.com/hahuk/passman-android into feature-android-autofill-and-gen-additions Signing Commit
…github.com/hahuk/passman-android into feature-android-autofill-and-gen-additions
Bring up to date with nextcloud/passman-android
…s unsupported. Get the IV directly from the cipher object instead.
…github.com/hahuk/passman-android into feature-credential-display-autoLink-url # Conflicts: # app/src/main/java/es/wolfi/app/passman/CredentialDisplay.java # app/src/main/res/layout/fragment_credential_display.xml
Feature credential display auto link url
…man-android into additional_features-1 Signed-off-by: binsky08 <[email protected]>
…additions' into autofill
Signed-off-by: binsky08 <[email protected]>
Signed-off-by: binsky08 <[email protected]>
Signed-off-by: binsky08 <[email protected]>
…e vault Signed-off-by: binsky08 <[email protected]>
Signed-off-by: binsky08 <[email protected]>
…er domains) Signed-off-by: binsky08 <[email protected]>
Signed-off-by: binsky08 <[email protected]>
…lUtils Signed-off-by: binsky08 <[email protected]>
Signed-off-by: binsky08 <[email protected]>
Snackbar.make(view, R.string.successfully_updated, Snackbar.LENGTH_LONG) | ||
.setAction("Action", null).show(); | ||
assert getFragmentManager() != null; | ||
try { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code seems to be repeated a few times, wonuldn't it be better if it was moved to it's own function?
I'm not sure if it might make sense to move it to the api library or if it's too specific for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you mean exactly?
I think its better to define the responseHandlers where they are now. They are all a bit (some more, some less) different and need custom variables from the "outer scope".
.setAction("Action", null).show(); | ||
assert getFragmentManager() != null; | ||
alreadySaving = false; | ||
try { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code seems to be repeated a few times, wonuldn't it be better if it was moved to it's own function?
I'm not sure if it might make sense to move it to the api library or if it's too specific for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replaced with one of the new response handlers
progress.setCancelable(false); | ||
progress.show(); | ||
|
||
AsyncHttpResponseHandler responseHandler = new AsyncHttpResponseHandler() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it make sense to move the API interaction to the API library on this context?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replaced with one of the new response handlers
app/src/main/java/es/wolfi/app/passman/CustomFieldViewAdapter.java
Outdated
Show resolved
Hide resolved
… ResponseHandler implementations