KeePass getting inadequate for 2022+ ?

[anon]

under absolutely no circumstances i would upload my account data to a remote server. even worse if the only reason to do that is convenience.
ever since the cloud stuff came up some years ago a lot of people seem to have lost any sense of security/privacy.

At this point and after several rants from me, I assume everyone is aware of the pitfalls and either accepts the risk or doesn't care But self-hosting on a home server is an interesting idea.

as to Master Razor's problem, one solution to what you want is sqlite. encrypt the database file or put it on an encrypted partition or similar and use an sqlite gui as client. that way you can have the exact table/field structure you want and performance shouldn't be an issue either.

Since he mentioned doing this with MS Access years ago, I assumed using a "regular" database was off the table for some reason...

[Sazzy]

We also have to be honest that self-hosting is not an option for most people. All/most of us here are computer savvy, but hosting your own solution just is not a viable option for the generic user.
They have no idea what they're doing and how to properly and most importantly, safely set this up. There's no point in self-hosting if the server itself isn't secure either. Most people don't even have a server or even a NAS and don't want to run their normal desktop 24/7

I get what you're saying about the cloud services, and I agree, but we also have to be realistic and accept that for a lot of people, this is the only option. It's either that, or trying to keep a txt file in sync over devices. Which for these users, will most likely mean:
- email
- dropbox
- onedrive
- other insecure things

That quickly turns into a major hassle, which in turn will result into them using the same password everywhere again.
Imagine telling the average user to just use sqlite Their heads would explode. And how will I ever log in on my phone

[Master Razor]

Since he mentioned doing this with MS Access years ago, I assumed using a "regular" database was off the table for some reason...

It's not. This is the best solution and I'm currently working on db as we speak.

I'll still need a gui interface for it.

// LE:

I just remembered that access database... It had another purpose at first, and only later it had been repurposed for DD.
I don't suppose anyone saved a screenshot? I would've liked to see that crud again. It reminds of simpler times.

[Instab]

self-hosting on a home server is an interesting idea.

i did neither mean nor mention that.

we also have to be realistic and accept that for a lot of people, this is the only option. It's either that, or trying to keep a txt file in sync over devices.

that's where the problem is. people simply have to classify a bit. do i need all my accounts everywhere? most likely not.
so the compromise solution for most people is to split things up. keep the crucial data offline and locked away and the less important stuff can be handled a bit more relaxed i.e. dragged over to the phone and other exposed locations.

Imagine telling the average user to just use sqlite

of course not. this was specficially for Master Razor because he asked for his own use.

[anon]

i did neither mean nor mention that.

I know, I mentioned it because BitWarden specifically offers and encourages it for those who don't trust "the cloud".

Self-hosting is indeed not for the average person... but they're not the ones who started this thread

[ephemeralsundown]

i would have dropped KeePass ages ago if it wasn't for its "merge database" feature. i only ever sync between devices when i actually need to login somewhere. also, KeePassDX for android is wonderful, way better than Bitwarden app

[Comply7879]

How is it better than Bitwarden app?