You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XC will open a database that contains invalid data in a time value, without reporting the error.
It would be better to advise the user that there is an issue instead of ignoring it.
See this KeePass issue: entry not a valid Base-64 string
cheers, Paul
The text was updated successfully, but these errors were encountered:
Is your desired action to prevent loading the database? What would the user do about the information the base64 is incorrect? Ignoring it and making it a correct base64 on save is the current behavior and, imo, the best behavior. Date time being incorrect is a very minor error and should not prevent loading of the database.
Agree that preventing loading is not ideal - this is the KeePass action.
Reporting the error to the user would allow them to find the offending app (and stop using it).
Repairing it is sensible, but some user interaction may be useful if it's a user configurable time.
droidmonkey
changed the title
Database corruption not detected/reported (entry not a valid Base-64 string error in KeePass)
Warn if database contains invalid Base64 represented dates
Dec 31, 2024
XC will open a database that contains invalid data in a time value, without reporting the error.
It would be better to advise the user that there is an issue instead of ignoring it.
See this KeePass issue: entry not a valid Base-64 string
cheers, Paul
The text was updated successfully, but these errors were encountered: