I never got over the fact that I somehow need to trust to an absurdly high degree a proprietary software to store ALL my passwords. Is this really a good idea?
You can use KeePass, but you’ll have to figure out a way to have your password vault available on other devices (can do it by using any cloud shares, i.e. GDrive). This way you’ll be in charge of almost every aspect of your passwords. But you’ll have to take care of backups and keep everything in sync.
I read a bit into bitwarden and it seems quite good, also with browser extension etc. Maybe I will think about my stance on password managers and give it a try
I’m sorry but no. I’m physically incapable of not moving the capital letter one space and I’m not entrusting my passwords to what I’ve irrationally decided IS named KeepAss. I just can’t.
It seems bitwarden is a bit more user friendly and also quite good in terms of security and privacy related issues (FOSS as well!) . Thanks for the help!
Even if they did, there’s some really smart technology at play here. I think your paranoia here is unjustified. I felt the same way until I read about their technology. At that point I felt comfortable using their service.
Anyway, iirc, 1password is architected in a way where a breach won’t actually disclose the passwords of their users, but I’m too tired to do the requisite double-checking to verify it
You are right in a way. I always assume company sysadmins have access to company data, even if they say the opposite, and I always assume there are undisclosed data leaks. Which may seem a little paranoid.
It’s like closing your car’s door when leaving it alone: Is it paranoid to assume that always there are someone willing to steal stuff?
No, I don’t think it’s healthy to move through life in such a paranoid state. If I thought that, I wouldn’t use a password manager and that would leave several problems unsolved, chiefly I would only be able to remember a couple passwords, opening my identity up for hacking several orders of magnitude likelier to actually happen than 1password’s entire technology stack failing at its one job.
A lot of weird hate for 1Password on Lemmy the past couple days. I highly recommend reading their white paper, I think most of the hate comes from ignorance of what they are actually doing.
It’s the choice between trusting one company (or if you self host, trusting yourself) to have their security all in order and properly encrypt the password vault. Using one password for every site you use means that you have to trust each of those sites equally, because if one leaks your password because they have atrocious password policies (eg. storing it in plain text), it’s leaked everywhere and you need to remember every place you used it before.
Good password managers allow audits, and do at times still get hacked naturally (which isn’t 100% preventable). Yet neither of these should result in passwords being leaked. Why? Because they properly secure your master password so it can’t be reverse engineered to plain text, and without the master password your encrypted password vault is just a bunch of random bytes. And even in the extreme situation it did, you know to switch to a better password manager, and you have a nice big list of all the places where you need to change your password rather than trying to remember them all.
Human memory is fallible and we want the least amount of effort, because of that we usually make bad passwords. Your average site does not have their password security up to date (There’s almost a 0% chance not one of your passwords can be found here). If you data is encrypted accordingly, it doesn’t matter if it gets leaked in any way or stolen by some rogue employee, so long as they do not have your master password. So yes, I’d say that’s a good idea.
So all my passwords are locked behind a single password? Isnt this essentially the same as using the same password for every site. In that they only need to cracl o e password to have access to everything?
For example, consider the case of a 1Password vault falling into the hands of an attacker. They do not have the option to just crack your password, as the password is mixed with a randomly generated value to ultimately derive the key. They would need to simultaneously brute force your password and that random value. This should almost be impossible. However, given access to a client that already has knowledge of the secret value, it would fall back to brute forcing the password.
You should be safe as long as your master password isn’t small, less than 15 characters. The longer the password, the better. Personally what I do is use a pass phrase to make it easily memorable, and then use it as a base to inflate security somewhat artificially.
Wrap the pass phrase around in brackets or symbols; mix lower/upper case; replace (or add to) a word in your pass phrase with one from a random other language, so instead of hello you type bonjour. Bonus points if you are able to replace even a few letters in your pass phrase with fancy diacritics, or fuck it add an emoji or two.
Then again there are a LOT of other factors which go into security. Theoretically the lyrics of song are decent as a pass phrase but there’s not much point if everyone knows what your favourite song is, or if you are learning Spanish then you’ll replace the English words with Spanish.
Unless you’re in a position where you’re targeted by nations or are working extremely high profile jobs like CEO or digital security you should be safe really with all these but as I said there’s a lot to keep in mind.
2FA is in the name, 2 factor authentication. A “factor” can be considered as proof that you are who you are. The more the factors provided, the more concrete proof the system has that the user is legitimate.
What a factor is is a more complicated. It can be broadly put in 3 categories (there’s more but we’ll ignore for now) :
something you know, like a PIN/password
something you are, like biometrics/eye scanning
something you have, like an ATM card or phone
The 2FA you are thinking of is probably the 1st (a password you know) + a PIN sent to or generated by something you have (a phone). If the 2nd pin was some you had created by memory like a password rather than a remote system generated one then it would be considered same as the first factor, it wouldn’t be multi factor.
So yeah it’s important that you keep both factors as secure as possible. A good password + a phone to generate TOTPs. I mean theoretically you can keep a password of ABC and keep 2FA on so hackers wouldn’t be able to get into your system but let’s follow best practices yeah? Use a password generator to make complex passwords for a login and enable 2FA.
In theory, yes but if you use a good password manager and have a strong master password the encryption should be practically impossible to break. The fact that you only have to remember one password means that this password can and should be a very strong one. 20+ characters with upper and lowercase letters, numbers and symbols should take centuries to crack.
The danger of using the same password everywhere is from leaks caused by poor security in one of those sites.
Passwords getting leaked are almost always unrelated to how strong the passwords are and has more to do with how those password are stored, and what protection measures they have against unauthorized people accessing them.
No one is ever going to “crack” your single password for your password manager as long as it is a strong password, though you might write it down in your wallet and lose it in a busy station, just like some administrator of a website might forget to close outside access to their mysql database containing unencrypted plaintext passwords.
I have been wondering as of lately, I’m an old Bitwarden user and I use their generated passwords which are just a random mess for my eye, anyway when a leak occurs I usually tend to type my known passwords to match it with the leak lists, but now all this being auto generated and I be totally clueless of which is which, how would I ever notice if one of those more secure passwords are leaked?
Does Bitwarden let you know of leaked passwords as Chrome and I think Firefox does? Because I don’t recall having this info in hand.
also, the length of the password is WAY more important than it being randomly generated as long as it’s not in a password dictionary somewhere. I use 20+ character passphrases that i can easily remember everywhere for instance
My strategy is to have a persistent short passphrase that’s within every password I use, and pair it with a silly bastardization of the service I have an account for. So, for example, if my passphrase were hunter2 (lol) and I had an account on Netflix, my password for Netflix might be something like hunter2NutFlex. Because of this, I can manage my own passwords in basic text as “code NutFlex” because the “code” portion is encrypted in my own fucking brain. If Netflix gets hacked, somebody has a password that only works with Netflix, and they’d need my text file as a Rosetta Stone to acquire my other passwords. Not impossible, but who the fuck am I and why would anybody dig that deep to do that to me?
I’m no IT expert, so somebody tell me if this is a stupid and overly vulnerable strategy. I thought I was pretty brilliant for coming up with this and rolling it out several years ago.
i am an IT person (wouldnt say expert) and i do this. password cracking time is based on the number of characters, not the type of char so you can do “abcdefghijk” and it will be more secure than “_a;” (both are still weak but my point stands)
all of this can be broken if you just use common passwords or plain english words since those are broken with dictionary attacks
It’s not the worst strategy (and is actually referred to as ‘peppering’ your password)… but if your primary use-case is websites and mobile apps, using a password manager like Bitwarden and randomly generated strong passwords is still a better strategy (and probably faster too, since you don’t need to type it out manually anymore, and/or remember which flex you used when creating your ‘peppered’ password).
This is a good approach if you have to login to services that aren’t via a web browser though - e.g. Remote desktops etc.
I’d say the approach is potentially vulnerable, but the tech isn’t quite there. The modern approach to password cracking is to take a huge dictionary, and run permutations on it, like change a’s to @'s, capitalizing first letters or adding numbers in the end. Any cracker worth their salt will have something like “add _netflix” as a permutation, too. I don’t think that anyone would have “NutFlex” in there, yet, but it’s possible if one of them stumbles on your leaked password from somewhere else.
As for “basic text”, do you mean like .txt’s? And do you store the entire password there? We do have viruses that scan for crypto wallets and it’s seed phrases already. It’s not too far fetched to imagine one that would cross-match any txt’s contents in the system with browser’s saved logins.
The most glaring issue I see is that the bastardization is effectively part of your password. With 1000+ passwords it’s going to be easy to forget (was it nutflix, sneedtflex, nyetflex or something?) and it’s going to be hard to find it if you don’t manage the codes properly. I recently had to scan over every single of my password manager entries (forgot a 100% random login, password and domain), and let me tell ya, It wasn’t fun.
You could possibly switch to a “client-side salting” approach, having a strong consistent password in you head, and storing a short but truly random suffixes for each service. e.g. text file named “Netflix” containing something like “T3M#f” and the final password would be something like “hunter2T3M#f”. At least that’s what responsible sites do to protect people who have simple/matching passwords. You could even store those suffixes somewhere semi-openly, like in a messenger as messages to yourself. But at that point, it’s probably easier to go with a password manager. Though that’s an option if you don’t trust those.
You could possibly switch to a “client-side salting” approach, having a strong consistent password in you head, and storing a short but truly random suffixes for each service. e.g. text file named “Netflix” containing something like “T3M#f” and the final password would be something like “hunter2T3M#f”.
I guess I’m not understanding how this is functionally different from what I already am doing. Why would your 12 character solution be more secure than my 14 character example? Is it just because NutFlex is two actual words, so a dictionary attack could crack that more easily? Or is it because it’s kinda close to the domain the account is associated with? Would I be significantly better off replacing those bastardizations with other random words?
Edit: and also, they’re saved as notes in my phone, and no I don’t type the whole password in. That would defeat the purpose of having a persistent master phrase as part of the password.
they’re saved as notes in my phone, and no I don’t type the whole password in
Then I must have misunderstood your approach. Is it like a single note with all the keywords only, then?
I guess I’m not understanding how this is functionally different from what I already am doing. Why would your 12 character solution be more secure than my 14 character example
Yeah, it’s because it’s close to the associated domain. The way I see it, this bastardization adds little entropy (there’s only so much possible variations) but also rather easy to forget. And a huge problem, in my opinion, is it’s using your mental capacity for per-site suffixes rather than master password.
A possible attack I see, is if I set up a site, say a forum called MyLittlePony.su with no password protection whatsoever, and lure you to register on it. If I scroll through the accounts and notice your password to be “hunter2MyLittlePenis”, I might go to paypal and give it a shot with “hunter2PenisPal”. Or, somebody whom I sold the database to, might. It’s extremely rare that anyone would even look at your password specifically unless you are some kind of celebrity, but it’s still a possibility. Maybe some future AI tech would be able to crack your strategy (I’ve tried, ChatGPT told me to fuck right off and FreedomGPT is not good enough yet)
Though you’ve said you also keep notes, which deals with the easy-to-forget part of the problem, so my first thought was to get rid of bastardization and add fuck-all amount of entropy by using a truly random suffix. That’d deal with the above problem. But, that’d mean that it’s your master password that is the suffix now, and you wouldn’t be able to access sites without the notes at all, hence it’d be easier to go with password manager at that point.
Then you look up the random string of 36 characters once, think “why did I make this one 36 characters” as you painstakingly type it in with a TV remote, then immediately forget it as soon as you’re logged in.
That sounds… even less secure, but admittedly I know nothing about it. How does it work? MAC address? Device type? OS? I think all of those can be spoofed…
If it’s a fairly inconsequential service (no payment/personal info, nothing lost if it gets hacked), you can just generate a far shorter password. Even randomly generated passwords can be remembered eventually if you have to type it enough times, and that’s still better than the same one.
If it’s not inconsequential, I’d be questioning if my money is well spent on a sadistic service that makes my life hell trying to have a minimum level of security. I would say that even if it wasn’t a generated password that you have to type over.
Some password managers support generating random passphrases like “correctbatteryhorsestaple.” They’re still a pain to punch in on a remote, but much easier to keep track of where you are in the password and avoid transcription errors.
Add comment