>>18154 (OP) >Now that we know KeePassXC isn't secure Do we? Can I get a rundown?

What's not secure about it?

>>18159 you can bruteforce it easily if you're password is less than 12 characters

>>18154 (OP) If you can't remember your password bitwarden wont help you either.

>>18170 That's every pw manager, yeah if your master pw is shit people can open it

>Now that we know KeePassXC isn't secure >posts pic proving that keepass is secure

>>18154 (OP) Why is tech literacy so low on the tech board? /g/ was like this too iirc

>>18170 You genuinely had me for a second, but this is just password etiquette and not a problem of the manager itself. >>18265 Lots of people come here just for advice or to talk surface level stuff, which isn't a problem in itself, but can be for shit like this

>>18265 For me it's that I know about some tech things and not others, tech also just makes me happy, but then I see someone building a program and I don't understand at all and it's like waow

>>18154 (OP) >storing your passwords >in one centralized location >in the distance, a soft glow intensifies

>>18290 My screenshot tool can decode QR. Nice image QR.

>>18154 (OP) >>18170 That's it?

>>18290 thonk

>>18265 chans are lowest of the lowest of brow

this is even funnier when you remember that keepassxc can export to a printable HTML document

>>18154 (OP) use google password manager

>>18154 (OP) I write mine down in an obscure physical book on my shelf in pencil so I can erase them when I update. Putting them on your computer is stupid

>>18154 (OP) Bitwarden is all you need.

>>18170 fuck you, had me worried for literally nothing

>>18290 >I seriously hope you guys dont scan this dont worry we dont

>>18170 This shit is pointless. You can bruteforce everything that is <12 Also why would you be worried about that when your database is locally stored? By the way AES and ChaCha20 are hard af to bruteforce

>>18170 that's it?

>>18290 I accidentally this QR code, should I run a guttmann pass on my SSD, rewrite it with zeroes and reinstall the OS on a hypervisor

The best password manager is your brain. Using details about your life that is easily remembered isn't a security risk if the password is decently long and has a bit of contextual additions like symbols that are still easily remembered.

>>18698 this doesn't scale well when you grow up and have dozens of bank accounts, utility accounts, business accounts, work accounts, shopping accounts to remember and your memory starts to suck you end up using the sameish password everywhere which will totally fuck you when a password leak happens

>>18720 I'm thinking about getting a password manager, but the ones that I see are closed source or hosted in servers. Wouldn't it be risky to trust in those services considering that the risk of a data leak is always there? What about just writing down your password in a book you have? If you want to make extra sure no one will crack it down write in cyrillics, nipponese, or whatever weird writing system

>>18154 (OP) >Now that we know that the offline open source software isn't secure >should we use the online only proprietary malware cancer instead? OP you fucking nigger. made me reply

it's hard to find faggots more annoying than freejeets honestly, even ponyfags and furries are less obnoxious than these subhumans.

>>18170 really nigga. got me scared for a quick second for no reason.

>>18170 you're an asshole

I use my grandpa's method for managing website passwords, come up with a base password, then add the first or last three letters of the website to the end of the password. And then capitalize the first letter if you need to.

>>18779 Sounds llike a wiser approach to tackle the password management question without using data grabbing services

>>18779 Tell us ur Google password then

>>18170 That applies to all secrets dummy No shit you can bruteforce things if their entropy is low enough

>>18735 Dude, OP's picrel literally shows you a FOSS password manager: KeePassXC, available for Windows/Linux/MacOS as well as Android and I think iOS. Another popular FOSS one is Bitwarden, but this one requires login (online) and I didn't like how it worked. I highly recommend KeePass.

>>18735 >What about just writing down your password in a book you have? That could be done as well, but it is less secure: anyone will have access to it (imagine a guest takes a picture or a burglar steals it), and it can be easily lost (unless you copy it in multiple books, but that will be tedious). It will also be harder to update in case you change your passwords or usernames/emails.

keepassXC with syncthing is peak comfy

>>18807 Why would i do that

Really suprised I didn't see a mention of the standard unix password manager: pass literally just some scripts that use gpg to encrypt/decrypt plain text, with an OTP support script and optional browser plugin support it's easy enough to backup your gpg secret and passwords, what more do you need?

>>18154 (OP) In the case of the OP image. KeePassXC was too secure.

>>19075 Isn't syncthing abandoned?

>>20314 >abandoned it just reached completion in its development.

>>18853 Will take a look at it then.

>>18170 With a good, solid wrench, extracting even >12 character passwords is trivial.

>>18648 that's password generation only. A password _manager_ does more than that.

>>20521 Watch him add like 7 lines and handle that fine.

>>18265 It's what happens when people start thinking technology is little more than running linux and posting screenshots of your desktop with a terminal open. It's just the imageboard alternative to people who think technology is little more than buying the new iphone and some electric car with an android tablet for a radio.

>>20602 auto-filling login fields with 7 lines?

>>18298 >>18696 What is it?

>>18154 (OP) Just write them down nigga

I just use pass with pass-otp and pinentry-rofi