Rootiest

Relatable.

Except it’s missing:

5b. Try 100 different things, none of which fix it and several of which will create other problems later

Oooh thank you!

Can’t believe I missed that

Like the other commenter said, typically websites are less locked down.

It’s simpler to sandbox the browser and prevent unauthorized software from running than to block out most of the Internet and deal with complaints all day about the web restrictions

I also use aYubiKey in VaultWarden but the key is not used to generate the encryption keys, only the master password is, so you don’t get that added security and benefit of the encryption keys rotating every time you save the DB.

You sure can.

But that’s not perfect.
Often businesses will lock down their computers to prevent unauthorized software from running at all, not just installing.

Ok that makes more sense lol

Ah, I couldn’t find that option.

I can add custom fields to an entry but I can’t designate them as “protected”

Of course I also thought at first that you couldn’t attach files but I guess you can, they just didn’t seem to transfer over from my KeePass DB

I’ve had some trouble with NextCloud as well. For me it just feels sluggish and bloated.

Someone in another thread here said “NextCloud can do everything, but it doesn’t do anything particularly well” and that seems to mirror my experience with it for the most part.

Of all the self-hosted containers I’ve set up NextCloud gave me the most trouble

I’m using randomly generated 64-character passwords with upper/lower-case letters, numbers, and symbols.

I prefer not to manually enter them every time.

Also someone could find and photograph your notepad and then all your passwords are compromised in one go.

and there even is a „no phoning home“ version that strictly runs locally.

Shouldn’t that be all the versions?

Why would a password manager app that uses a local database need to phone home?

I have both set up right now.

Things I like better about KeePass:

KeePass doesn’t use the cloud, you don’t have to worry about the server getting compromised or going down because there’s nothing public-facing to hack. You always know where your password database is.

KeePass lets you encrypt the database with not only the master password but also using the challenge-response from a YubiKey. That means every time you save your DB the encryption key is rotated and the DB is actually encrypted by two authentication factors.

While both can add custom fields to an entry, I like that KeePass has the option to set fields as protected so their contents are hidden like the passwords.

Things I like better about VaultWarden:

Convenience.

You can log in to your VaultWarden account on any device from the browser. KeePass requires some software to access the DB.

The VaultWarden companion software is just better. It just does autofill better. KeePassXC/DX work well but just not as well as the BitWarden software.

Other thoughts:

Syncing passwords between devices with KeePass requires 3rd party software like SyncThing. If you break/lose/etc your VaultWarden server you could lose all your passwords with it.

Always make/test backups.

I suspect cigarettes generated a lot more litter but with a lot less precious metals in it

Yeah this is probably my biggest.

Device which things can be hosted on a local server and which are best on a vps

But where is the safe huh?

See? Gottem

I didn’t mean after you logged in… I meant as the default login option to a new Linux box.

Ah ok. I misunderstood.

As to the other bit, Google hasn’t disallowed passwords and I don’t think we’re at a point where they would.

But I mean ideally you have multiple PassKeys so if you lose one or you computer/phone dies you have a backup.

I keep a hardware key in a safe that can be used as a backup key to my accounts

PassKeys work on Linux… you just need to use a compatible browser which is most these days.

It’s also a fido standard so it isn’t really a Google thing, Apple started using them before Google even.

I use Kopia

Which character are you going to change?

Go for it!

I generated it in KeePass for this comment and actually interestingly it looks like Lemmy butchered/sanitized/modified it as well

PW:

u#'o*zaQMyPC"fnw?Cu9OSrxYeEDCe6yXgzQYL4NxP?k%sx+'dBKfdru0CUmD&

If the server won’t take a 64-char pw with letters, numbers, and symbols then is it even worth using?