Do you just go around looking for KDE users to argue with?

The fact that the company Valve went with KDE instead of GNOME for there popular linux device seems to indicate that it is at least stable. I could get some user testomonies on /c/Linux about KDE if you want?

Recently they officially added a module to censor stuff on an individual instance basis…

KeepassXC honestly is more userfriendly IMO.

Oh you just reminded me, KepassXC and DX Doesn’t demand you to create an account and log in to access your vault 😄

Self-hosting KeePassXC requires installing one package and backing up one file. I expect that requires less technical skill and is doable for more people than to self-host Bitwarden.

Hoe do you sync it? I’ve been meaning to make the switch to these for a long time now, but still not gotten around to it.

I ran into issues when using Bitwarden for the first time, i don’t understand why, i just like having my password vault close to me, KeepassXC and KeepassDX just makes things a little more painless

I will still prefer KeepassDX and KeepassXC

It gave me trouble when i tried to log in ob my account, and i prefer having the database WHERE I CAN SEE IT

Nope, sonce your Keepass database is store locally, all you need is Syncthing, you won’t beleive how easy it is to use.

You don’t. KeePass databases can be easily shared totally offline.

However, it all depends on “how easy” you want the sync to happen…

There are many ways to “sync” KeePass databases, basically you just have to copy password database among the devices, which can be done totally offline.

• HARD - Manually copy the KeePass database to the devices
  • Can be accomplished via any Network connection or USB cable connection
• EASIER - Put the database on any file sharing service that’s available on your devices, and sync that
  • The file sharing service can be available on the internet (Google Drive, OneDrive, iCloud…), but it also works with any file sharing service that’s not connected to the internet (e.g.: local only Nextcloud server, or not even that, using Syncthing if that’s your thing…, which would not even require a local server)

So, I’ll just give one example.

If you have 2 devices:

• Linux PC
• Android Phone

You can use KeePassXC on the Linux PC, and KeePassDX on the Android Phone, and have a copy of your kdbx file (the encrypted database) on each device, manually copying the newer version whenever there are changes on them.

Issues that might happen: consistency between the files in case you make changes to both databases and forgot to sync manually previously. There’s no easy way to handle this currently afaik if you are doing manual syncs… I’d suggest maintaining one of the databases as “kinda read only”, not performing edits on it unless you can immediately copy it to the other one.

You can do the same thing above, but instead of manually copying the files among the devices you can use Syncthing… Or if you have a local Nextcloud server, you can use that to share the files, which is pretty easy to use to ensure consistency if you are using KeePassXC and KeePassDX, since if you open the database on Android using KeePassXC directly to the “file system” that links to the Nextcloud folder, it will always automatically retrieve the newest version to your device if there has been any change and if your local Nextcloud server is reachable, otherwise it just uses the local cache, and you will know it’s using the local cache and was not able to sync.

It’s not that it’s inherently safe, but that Microsoft is inherently not.

Perhaps this will change drastically with immutable distros

Check out GL.iNet, good hardware and ships with OpenWRT but with their own WebUI. I set up my dad’s place with their router and an access point and I don’t remember the specifics, but it was really easy to access LuCI and do the advanced stuff.

The Turris Omnia is an open, powerful router that comes with OpenWRT.

Turris adds an additional UI and features beyond that, but the OpenWRT UI is still available and the stock firmware can be completely replaced with OpenWRT if so desired.

It’s a bit pricey but has great specs (1.6 GHz dual core, 2GB RAM, 8GB eMMC) and is an excellent device for tinkerers with headers exposing UART, JTAG, GPIO, and more. It has three internal mPCIe ports as well.

I am not affiliated with Turris but just happened to stumble upon a new one at a garage sale a couple of days ago. Lucky find and I’m excited.

They’re broken for me as well. They’re missing the https:// at the beginning, which I think is the problem. Here are the links:

https://shotcut.org

https://openwrt.org

I get the thought, but your phone can also have a security breach at any moment, ESPECIALLY because normal user error is by far the weakest and most often exploited attack vector.

Bitwarden’s vaults are also encrypted with the option for even stronger argon2id encryption. Bitwarden themselves can’t access them or reset them. It is open source and most importantly, audited. KeypassXC has only had one audit ever. (Though that passed and I would also definitely recommend keypassXC, it is great software security-wise)

The database is stored, encrypted, once on their server and once to each device you sync to, so it is available locally.

Even if they had a security breach, by design the assailant couldn’t access your database any more than they could access your keypass database.

You can also self-host it which would bring it exactly to the level of keypassX variants as far as attack surface.

Not to mention with bitwarden, you will also only need one key. That is the whole point of a password manager.

“It is available locally and a lot better…” is simply untrue. They are both great options. Just whatever works best for the person. Bitwarden has a ton more QoL options and enterprise options, plus separate, shared password databases and such for families and companies. Again, just as secure.

While I personally use KeepassXC and Keepass2Android on mobile devices (as with KeepassDX there is no reliable way of syncing the database that I know of) to other less tech-inclined people I’d always recommend Bitwarden as it is much more suitable to most people’s usecases.

I have a lot of experience with both. As a tech savvy user, I slightly prefer KeePass. Syncing between devices is slightly more painful, but I find it to be more reliable, and it doesn’t have the attack surface that Bitwarden does. (While encrypted, Bitwarden still really wants a web server and a local database connection.)

VaultWarden is probably better for those who can’t be bothered to move a file around and want direct browser integration. With KeePass when you need a password, you’ll make sure the username has focus and then alt+tab to KeePass and hit “autofill”. Some sites won’t take “username{tab}password{enter}” and you’ll have to customize the configuration.

VaultWarden is better at prompting you to add new passwords. I prefer the workflow that’s encouraged by KeePass, where you open the app first and use the app to open the URL. (You can do this in VaultWarden too, but it’s less obvious.)

What’s not simple about it, as a password manager? Pop in the name/uri, pop in a username, pop in/generate a password Bingo bango Is there a level of complexity I’m missing, or alternatively is there a simpler approach?