Conversation

Notices

1. Embed this notice
   Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 05-Jul-2025 09:28:26 JST Miakoda

   A goof with my password manager made me think about it....
   You REALLY need to get your shit together with passwords.
   Stop using ones you can remember. Use big stris of random characters and put them in a GOOD password manager. Not the garbage Chrome came with, turn that bullshit off.

   I recommend KeePassXC if you're comfy fiddling with your computer a bit, and BitWarden if you're not.
   KeePass, you sort out your own syncing.
   Bitwarden does it for you, and hasn't been named in data breaches.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 05-Jul-2025 09:33:35 JST Miakoda

     in reply to

     Bitwarden is free for most functionality, $10/yr for premium which can also do TOTP 2FA.

     KeePassXC also does TOTP $0!. It has KeeShare for syncing. A tip for newbies... You DON'T sync over the database file. You sync that KeeShare file instead. That tripped me up when I started.
     KeePassXC reads what changed from that KeeShare and then updates the database on the computer.

     I highly recommend using the backup settings. If you fuck up KeeShare, you have that back up file to recover with.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 05-Jul-2025 09:36:40 JST Miakoda

     in reply to

     You can use rsync, or NextCloud, or really any other method of making the same file appear on multiple computers. Use that to sync the KeeShare file.

     If you manage passwords for family members, maybe an elderly parent... You can have more than one database, and you can get KeePassXC, with it's browser extension, set up so the elderly person doesn't need to understand it all. You can update their passwords and have it sync over without them having to understand it.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 05-Jul-2025 09:56:31 JST Miakoda

     in reply to

     • hazelnot :yell:

     @hazelnot So KeeShare files contain what changed, along with a signature. When KeePassXC sees the KeeShare file, it updates the database on that machine. If 2 machines try to write to the KeeShare at the same time, or the KeeShare gets overwritten, you didn't just corrupt or lose your entire database and the machine with new changes can simply attempt to perform the KeeShare process again.

   • Embed this notice
     hazelnot :yell: (hazelnot@sunbeam.city)'s status on Saturday, 05-Jul-2025 09:56:32 JST hazelnot :yell:

     in reply to

     @hellomiakoda wait what's a KeeShare

     I've just been putting my KeePass file itself on a file server and syncing that 💀

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 05-Jul-2025 09:58:53 JST Miakoda

     in reply to

     • hazelnot :yell:

     @hazelnot For the sake of it being easier if a failure occures, I like to name my database files
     DatabaseName.hostname.ext (I cant remember the extension for KeePass files at the moment) and the back ups it writes before saving to the database as Databasename.hostame.ba kup.ext

     If shit hits the fan and I just have a bunch of recovered files, if I know Skye was the last machine I saved passwords on, that's the file to start with.