Conversation
Users can now seamlessly import CSV files from their browsers into KeyGo and conveniently export their passwords to CSV files as well.
Users can now seamlessly export and import encrypted .keygo files.
Prior to this change, the application would request user authentication before issuing a security warning when exporting passwords in CSV format. With this update, the order of these actions are reversed, ensuring that users now receive the security warning first, followed by the request for authentication. This change enhances the user experience and prioritizes security awareness.
This change ensures that users receive an accurate message following a successful import operation.
This change ensures that users are required to set a password before proceeding, making the dialog non-cancelable to prevent users from saving an empty file
(cherry picked from commit 5d3fe53)
(cherry picked from commit 57d771f)
(cherry picked from commit 238d01f)
(cherry picked from commit 3e86c6a)
This fix addresses the problem where the application would erroneously export and import the ID of an element. This issue previously caused conflicts when attempting to import an element with an existing ID in the database, resulting in the overwriting of database entries.
This fix addresses a bug that caused the dialog to close prematurely when no password was entered for exporting or importing a file. Now, users have the opportunity to reenter a password, ensuring a more user-friendly experience.
This introduces a more flexible approach for defining secure, password-encrypted backups, as well as standard CSV backups. Additionally, the password request process has been moved to a lower level within the SecureDataBackup class, further enhancing the implementation.
This addresses an issue that occurred when attempting to import a backup by clicking on a .keygo file. Previously, the application would occasionally throw a "Permission denied" error.
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.
This closes #6 and #16