- May 27, 2013
- 347
Yes, I understand and I won't do that.Dont think of last pass as a Password Manager think of it a a IQ test, last pass has failed on security lied and been far from truthful about security incidents, why would you trust them with your data? Would you ask a fraudster to look after your money ?
Functionalit wise, Lastpass is great. In terms of security, any cloud password manager is not to be trusted no matter how they market it.Hello guys,
I have a doubt: I didn't know about Lastpass, I only used Bitwarden (I'm sick of it) and offline password managers like KeePass. I created a random account just to check how Lastpass works and I liked it. Is anyone still using it? Is there any risk? If so, is there a product similar to LastPass?
I was reading on the LastPass blog and from what I understand, even if the data has been leaked, hackers will not be able to access the vault since there is no way to know the master password of each vault because LastPass is zero knowledge, but I could be wrong because I never used the service. What opinion can you give me about this?
Thank you all!![]()
Cool, that's good to know. That's what I thought, as a password manager (in terms of functionality) it seemed excellent to me, but it has this other downside that you mentioned.Functionalit wise, Lastpass is great. In terms of security, any cloud password manager is not to be trusted no matter how they market it.
Users complained on Trustpilot on SP functionality on Mac. Anyway, give it a try and see how it works. Then try Enpass and see how it works and then you can decide what works best fir you.Cool, that's good to know. That's what I thought, as a password manager (in terms of functionality) it seemed excellent to me, but it has this other downside that you mentioned.
I have a lifetime license of SP, however, I don't know if it works on MacOS as well.
I would like something similar to LastPass that syncs between my devices (android, mac and windows). The way is to continue using KeePass despite the difficulty in synchronizing between devices.
While the hackers don't know the master passwords, by having copies of the vaults in their possession, they have an unlimited amount of time to crack them. Think about how bad people are at coming up with secure passwords on their own, and now imagine how many LastPass users were using weak master passwords when the vaults were stolen. The fallout's not going to be pretty.I was reading on the LastPass blog and from what I understand, even if the data has been leaked, hackers will not be able to access the vault since there is no way to know the master password of each vault because LastPass is zero knowledge
Exactly, it is a gample I am not willing to take.While the hackers don't know the master passwords, by having copies of the vaults in their possession, they have an unlimited amount of time to crack them. Think about how bad people are at coming up with secure passwords on their own, and now imagine how many LastPass users are using weak master passwords. The fallout's not going to be pretty.
Really you are right.Exactly, it is a gample I am not willing to take.
But what users are doing is unrational. Most of them migrated to BW, which is also cloud-based. The fact that jt is open source does not make things any better. The data is stored in the cloud and the same thing can happen.
"We have determined that an unauthorized party,[U] using information obtained in the August 2022 incident, was able to gain access[/U] to certain elements of our customers' information."
Ultimately it's a personal decision. There's always risk no matter where you choose to store your data. Obviously this LastPass breach shows how damaging it can be if you choose to store your data on someone else's server, and that data is accessed by a malicious actor, but that doesn't mean it's guaranteed to happen. But even those who opt to store data locally are still at risk of malware infecting their system and exfiltrating that data (which, again, doesn't mean it's guaranteed to happen, but the risk is still present).Exactly, it is a gample I am not willing to take.
But what users are doing is unrational. Most of them migrated to BW, which is also cloud-based. The fact that jt is open source does not make things any better. The data is stored in the cloud and the same thing can happen.
I really like KeepassXC, but the absense of dedicated mobile apps made me look elsewhere.Really you are right.
Right now I'm using KeePassXC (because it works on both Mac and Windows) and I keep everything offline with backup copies on other external devices that are also protected by Bitlocker.
Even though the synchronization between the devices is a little inconvenient, I'll keep it that way, for the sake of greater security.
Thank you for your answers and for your attention. @Divine_Barakah and @Arequire.
But storing password locally gives more control and peace of mind.I don’t think the problem is being a cloud pw in itself. But rather how badly Lastpass handle the security of its users.
If they had
- Encrypted website URLs
- Properly notified users of weak master passwords
- Properly increase all users password iterations
Could this had prevented the hack? Nah, I don’t think so. But the hack wouldn’t have been as catastrophic as we have today.
You are right. Offline password managers have attack vectors, but they are simply not prone to the same attack vectors of online password managers.Ultimately it's a personal decision. There's always risk no matter where you choose to store your data. Obviously this LastPass breach shows how damaging it can be if you choose to store your data on someone else's server, and that data is accessed by a malicious actor, but that doesn't mean it's guaranteed to happen. But even those who opt to store data locally are still at risk of malware infecting their system and exfiltrating that data (which, again, doesn't mean it's guaranteed to happen, but the risk is still present).
Remember not all users want control. (it’s the reason why HIPS aren’t popular) they rather have convenience.But storing password locally gives more control and peace of mind.
A havk is still a hack. If for example Bw was havked and they informed users that no data was accessed? What would you do? Youll have doubts and most likely you will panic.
Thus, it is sound to keep you data locally stored.
You are right. Offline password managers have attack vectors, but they are simply not prone to the same attack vectors of online password managers.
A server containing the dafa of millions of users is a valuable target.
You have a point here. Tbh if users are responsible of taking care of syncing password using for example Enpass, they might lose all of their passwords. Cloud password managers take care of that but that comes at a price.Remember not all users want control. (it’s the reason why HIPS aren’t popular) they rather have convenience.
I remember a few years ago. In another security forum, a user doing and suggesting what you describe here. Splitting passwords between password managers and IRLI will sync my passwords to the cloud no problem, but I will do the following, keep only a part of the password like this "3zN$KSohZn!vR78&cvXC" the rest that would be suffix or prefix would be basically like this + U4!5J%x^s* I will memorize the rest in my memory and if the cloud service is hacked good luck to the hacker![]()
For Keepass, take a look at Keepassium and Strongbox available on iOS, not sure about Android.I really like KeepassXC, but the absense of dedicated mobile apps made me look elsewhere.
For Android it is Keepass2Android or KeePassDXFor Keepass, take a look at Keepassium and Strongbox available on iOS, not sure about Android.
Yes, exactly it was in security forum, I just remember where, later I saw it on Youtube, the curious thing is that the person who uses it this way is a developer seems more paranoid than me.I remember a few years ago. In another security forum, a user doing and suggesting what you describe here. Splitting passwords between password managers and IRL