Herbert Poul
Herbert Poul
When changing the master password users should be able to choose a keyfile. We should also offer a way to generate a keyfile.
When there is enough horizontal space we could have the group list all the way to the left.. so we would have: Group list | Entry List | Entry Details...
I guess the source of truth is the build file.. but it would still be nice to remember which dependency is required for what.. https://github.com/authpass/authpass/blob/1dbf03339a077285f75764da7a327750f7167769/.github/workflows/linux.yml#L33-L42 * keybinder-3.0 for `hotkey_manager`
When the user creates a new file by default we simply put it into the application document directory. Now that #260 is implemented users can remove them from the `recents`...
If anyone is interested in this, please 👍️ or comment ;-) Imho copy/paste seems to do the job pretty well
see also * #3 and * #46 (last one might make this issue irrelevant, if we simply do not ask for a password upfront, but only during the first save)...
Right now only one authentication/connection information is stored for each cloud storage type. It would be nice if users can configure multiple e.g. webdav accounts from which to load kdbx...
Seems like this is not implemented in google drive v3: * https://issuetracker.google.com/issues/36759400 * https://issuetracker.google.com/issues/126874315 maybe switching to google drive v2 would work. https://stackoverflow.com/questions/38539158/how-to-update-already-existing-file-in-google-drive-api-v3-java
Create a password backup using [Shamir's Secret Sharing](https://en.wikipedia.org/wiki/Shamir%27s_Secret_Sharing) this way a user could create e.g. 4 backup codes he can share with his friends and require at least 3 of...
It should be possible to automatically enter passwords on windows using some kind of auto type feature. E.g. a configurable see also #13 for the mac version of this issue.