KeePassXC 2.6.1
81–90 of 119 posts
Re: KeePassXC 2.6.1
#82Earlier quoted context omitted.
Started using Keypass about a year ago, I really like it. Just wondering if Dropbox is considered a safe place to store the DB files? I did this for a while, but then I got paranoid and switched to something fully encrypted. For sharing between devices I found Firefox Send to be useful (before it went down, hope it comes back), also Keybase filesystem is one of my go-tos as well. Maybe I’m being overly cautious, but…
I store the KDBX file in Dropbox, store the key file elsewhere, and use a strong password. Without the key the database file is useless.
Re: KeePassXC 2.6.1
#83I’ve been using KeePassXC almost as long as it’s been available, and couldn’t be happier. Database stored on my NAS and synced to Dropbox for when I’m out, gives me access on all my devices without having to worry about whether x or y service will still be around in a year or 2.
Started using Keypass about a year ago, I really like it. Just wondering if Dropbox is considered a safe place to store the DB files? I did this for a while, but then I got paranoid and switched to something fully encrypted. For sharing between devices I found Firefox Send to be useful (before it went down, hope it comes back), also Keybase filesystem is one of my go-tos as well. Maybe I’m being overly cautious, but…
Fwiw, I've lately been using Resilio Sync, which is BitTorrent style peer-to-peer between devices I control and encrypted over the wire as well. It also supports advanced encrypted shares where you can even have "know nothing" devices that help to seed/participate in your shares but can't read/write inside them, as an interesting tool in "personal cloud hosting".
Re: KeePassXC 2.6.1
#84Earlier quoted context omitted.
How can anyone switch to bitwarden given how complex it is to switch back in the future? I love keepass because I am allowed to export my DBS to any other provider with ease. For bitwarden, there is not a good export system (that includes attachments,images...),meaning that I would be vendor locked.
What vendor lock-in? They make it plainly clear how to export your data from BitWarden: https://bitwarden.com/help/article/export-your-data/ Personally I think it would be awesome if Bitwarden gave you the option to export your password vault as a KDBX4 file. What's the best way to fund a bounty program for adding this feature to Bitwarden?
Re: KeePassXC 2.6.1
#85I have a free drop box account and use it to store kdb file. What is a better alternate if I want to access to kdb file from more than 3 devices (combination of windows + ios devices.)
Re: KeePassXC 2.6.1
#86I have a free drop box account and use it to store kdb file. What is a better alternate if I want to access to kdb file from more than 3 devices (combination of windows + ios devices.)
Syncthing
Re: KeePassXC 2.6.1
#87I have a free drop box account and use it to store kdb file. What is a better alternate if I want to access to kdb file from more than 3 devices (combination of windows + ios devices.)
Re: KeePassXC 2.6.1
#88Earlier quoted context omitted.
Syncthing
I did read the other comment about syncthing; but that requires setting up a server. Do not want to go that route.. :)
Re: KeePassXC 2.6.1
#89Currently running KeePassX. Maybe I'll give this a whirl. The key concept with the KeePass family of projects is that your passwords remain on your device, and don't get synced to some cloud you have no control over.
KeePassX won't prompt you at all and silently drops all those changes, whereas KeePassXC will ask what to do.
KeePassXC also seems to immediately save changes upon adding new entries whereas KeePassX requires an explicit .
Re: KeePassXC 2.6.1
#90Earlier quoted context omitted.
Source code access, and being free of charge seems to be the main things you would get compared to 1Password. Also, great Linux support (from what I've heard 1Password only recently even added a Linux-compatible client). But to me it sounds like you have a solution you are very happy with, and you don't mind paying for that solution, so my recommendation would be to stick with it. Although, as a happy user of KeePass…
Good question. I can't think of compelling reasons why a standalone user, or a small team, would switch to 1Password if they're already happy with KeePassXC.