keepassxc
keepassxc copied to clipboard
keepassxreboot
Allow Copy/Paste of entries and groups between open databases
#171 talks about the problem of a database getting out of sync
The usual workaround to this is to make another checkout of the database, open it, and then copy over the information.
Expected Behavior
- It should be possible to copy an object (or tree) and paste it into another database
Current Behavior
Everything has to be done by hand
Does the merge feature do what you want? If not, please state in more detail how you want to copy things from one database to another.
I think it's about being able to copy/paste between databases, like KeePass (Windows / C#) can, with Ctrl-Shift-C and Ctrl-Shift-V. I tried that key combination in KeePassXC and nothing happened.
Merge functionality seems to be about reducing the number of databases, whereas generic copy/paste functionality can be used to split a database into several databases, in addition to manual merge of course.
This wouldn't be that hard to implement since it's very similar to doing a merge on a tree or single object in the database. I think this should be reopened.
This should also be accomplished via drag/drop between open database tabs.
IMHO this function is desperately needed! especially in our company i have regularly to move entries between databases because of different projects, change of access levels etc... copying every item of bigger entries one by one is really tedious and error-prone!
i know, a kind of a workaround is exporting, deleting the not needed entries and importing the remaining ones to the new database. DISCLAIMER: i really don't recommend this (especially not on unencrypted storages) because you are storing your entire database unencrypted on your hard drive! and at the latest with forensic tools it may be easy (even after quite a while) to recover the whole unencrypted database. --> and i don't want to use KeePass (even not for this one task) because it looks sooo ugly and does not integrate a bit into my linux-desktop. :frowning_face:
btw: an option to copy/move only the current entry or including the whole history would be the icing on the cake. :wink:
@DJCrashdummy it sounds like you have an excellent use case for keeshare.
@droidmonkey is there documentation any where on the Keeshare? I find issues for it in the issue queue and notes about it in the change log but I cannot seem to find any documentation on how to use it. Just looking for someone to point me in the right direction.
@droidmonkey Ah ha! I just found the pull request that started KeeShare with a link to the updated Quickstart guide, however this appears to not yet be in the Quickstart Guide on the keepassxc.org website.
@droidmonkey Does KeeShare work with any Android apps yet? Or should I open an issue for that with the Android apps?
I don't think so, but you can open the database separately from the share as well.
Drag&Drop is already possible Ctrl+C/V may be an interesting feature to implement.
Drag&Drop is already possible Ctrl+C/V may be an interesting feature to implement.
Drag&Drop seems to be unstable. I think I used it in the past, but when trying now it does not work. Using Fedora 32, GNOME on wayland and keepassxc 2.6.0 I cannot drag and drop entries between two open databases.
Qt bug with wayland
I found https://bugreports.qt.io/browse/QTBUG-80303, but following references and MR, that bug should be fixed for Gnome 3.34 Fedora 32 is 3.36...
i wanted to mention this separately because it can become critical in some cases: although copy/move of entries is somehow possible, it just copies the current state of the entry, not its history! - so be aware, that you'll lose the history (which is really "unfortunate", especially if you move an entry).
unfortunately, i must insist on yes!
i'm using KeePassXC - Version 2.6.2 Revision: e9b9582 installed via PPA, and tested it extensively before posting.
as already mentioned a while ago: it can be a nice (optional) feature regarding convenience to just copy the current state without the history... but this being the default even when moving an entry can lead to some kind of a disaster.
As stated in my duplicate bugreport #8317 I would go for the following default:
- Moving when dragging & dropping inside the same database
- Copying when dropping in another database
- Defaults can be overwritten/forced by pressing CTRL (copy) and SHIFT (move)
Benefits:
- It is intuitive and easy (my mum can do)
- You will not loose data accidentially
- You could still move the data by holding shift (currently you need to hold CTRL to copy)
- Its the same behavior as filesystems do
I'd argument that moving is more common for the same database while copy is for another. This behavior is similar to USB Stick handling in filesystem managers. I was really lost when I used the feature the first time, and my original entry was gone. Luckly I am a tech-guy who knows that I need to press CTRL. My mum does not. My mum would just drag it. And if she really wants to move the entry, she would copy it and delete it in the old. But in most cases she is safe to not loose data. That's KISS.
Do you guys agree?
That's certainly my expectation. The request is just about copying from one database to another. I didn't envision changes in behavior for operations within a single database.