Slashdot Mirror
LastPass Reporting a Security Breach, Including Authentication Hashes and Salts
hawkeyeMI writes: LastPass, the popular password manager, has been hacked. The company says that the “vast majority” of users are safe, and has posted a notice which begins: "We want to notify our community that on Friday, our team discovered and blocked suspicious activity on our network. In our investigation, we have found no evidence that encrypted user vault data was taken, nor that LastPass user accounts were accessed. The investigation has shown, however, that LastPass account email addresses, password reminders, server per user salts, and authentication hashes were compromised."
Modern app appers app apps using other apps in The Cloud, so you can't get apped by apping apps!
Apps!
Store it on "the cloud"! Everything will be fine!
Who the fuck would think it's smart to use some web service like that, where some third party ends up with your passwords, even if they are encrypted in some way?
Storing passwords in the cloud... What could possibly go wrong?
...where I regularly store hundreds of passwords, has not been hacked. Recently.
I don't know how many people that I know who use one of these things that I say over and over, it is just too juicy a target to hack. Way too juicy.
It's not a big deal. I just use it for sites where I don't care if someone hacked it really (forums, news sites, etc).
Anything financial (banks, credit cards, vanguard, paypal, etc) stay out of there for sure, though.
I told you so.
I'd like to take this time to recommend an excellent open source project called KeePassX.
https://www.keepassx.org/
It's a password vault application. Remember local applications, they run on your computer, that you physically have to be at to use(usually).
The Information Revolution will be fought on the command line.
We are confident that our encryption measures are sufficient to protect the vast majority of users. LastPass strengthens the authentication hash with a random salt and 100,000 rounds of server-side PBKDF2-SHA256, in addition to the rounds performed client-side. This additional strengthening makes it difficult to attack the stolen hashes with any significant speed.
Salting is nice, but when the attacker gets both the hash and the salt, they can attack specific users. Still, the 100k rounds of SHA256 seem decent.
Would bcrypt be any better than PBKDF2 here?
because we need an excuse to say "we don't own this failure, it wasn't us".
I find ssh'ing into my own raspberry pi with keepass-cli http://sourceforge.net/project... the best way to get passwords so far. Slow but trustworthy. I sure wish that was not a sourceforge project though.
I am obviously unable to use something online, like Last Pass and 1Password.
It little behooves the best of us to comment on the rest of us.
I'm the submitter. I'm a LastPass user and I'll stay that way. If you actually read the article you'll see that things are under control. This is the second time LastPass has reported an attack that I can remember, and because of the client-side encryption and so on it's not a huge deal. Bravo to them for their proactive stance and sound methods.
Error 404 - Sig Not Found
this is the last pass manager i use
Does anyone know if the private keys of any SSL certs used by their web site have been affected at all?
How can we be sure that we're communicating with the actual LastPass web site?
If you actually read the article you'll see that things are under control.
I have this great real estate deal for you. There's this bridge that's about to come up for sale soon and I want to extend you an offer before I let the news out...
My password is 12345. Was it hacked today?
"We’ve commissioned a write only off-site aggregated log server which can only be accessed via the console. This will allow us a guarantee that any logging is intact." ref
It's a strange idea to store passwords in the cloud anyway. I use these simple scripts in Ubuntu. Could work on Mac too, and I had a Windows/Perl/batch-file version long ago:
$ cat `which p`
#!/bin/bash
[ -d /media/truecrypt1 ] || t on
# accept up to 3 arguments, and filter on all 3 /media/truecrypt1/p /media/truecrypt1/p | grep -i "$2" | grep -i "$3"
if [ -z "$2" ]; then
grep -ni "$1"
else
grep -ni "$1"
fi
$ cat `which padd` /media/truecrypt1 ] || t on
#!/bin/bash
[ -d
echo `date +%F` " $@" >>/media/truecrypt1/p
And to mount the truecrypt volume:
$ cat `which t`
#!/bin/sh
file=$HOME/timecode
tcvol=/media/truecrypt1
do=$1
case "$do" in /media/truecrypt1
"on")
if grep -q
If you have a real argument present it please. I encourage you to understand how LastPass actually works, and not how you think it works based on not reading TFA (obviously from your statement).
There is a bit missing in the post above:
$ cat `which t`
#!/bin/sh
file=$HOME/timecode
tcvol=/media/truecrypt1
do=$1
case "$do" in /media/truecrypt1 < /proc/mounts ; then ;; ;; ;; ;;
"on")
if grep -q
logger -t truecrypt "$0 Starting tc: already mounted"
exit
fi
logger -t truecrypt "$0 Starting tc"
DISPLAY=:0.0 truecrypt $file
"off")
t=$(find $tcvol -type f -printf "%TY-%Tm-%Td %TH:%TM\n" | sort -n | tail -1)
truecrypt -d
if [ -n "$t" ] ; then
touch -d "$t" $file
logger -t truecrypt "$0 Stopped tc and set mtime to $t"
else
logger -t truecrypt "$0 Stopped tc; no mtime to set found"
fi
"status")
truecrypt -t -l
"*")
echo "Usage: $0 on|off|status";
logger -t truecrypt "Bad option '$do' given to $0"
exit 1;
esac
LastPass of course is going to be a target; but if you used the product as recommended with 2nd factor authentication and not reusing your master password elsewhere you don't have anything to worry about. LastPass is handling this in a measured, logical, efficient manner - and as always, they err on the safe side. Of course, this being the internet, you have the usual suspects crying chicken little, the sky is falling.
backdoor into the encryption. It's only a matter of time before hackers locate it and fling it open to let the animals in.
There are no secrets. There is no privacy.
I'm the submitter. I'm a LastPass user and I'll stay that way. If you actually read the article you'll see that things are under control.
This is the second time LastPass has reported an attack that I can remember, and because of the client-side encryption and so on it's not a huge deal. Bravo to them for their proactive stance and sound methods.
Not only that, but even if the encrypted vault were compromised along with the hashes/etc (allowing somebody to start brute-forcing them), I could easily use lastpass to identify all my accounts and the last change date for each. Since almost all my accounts use random passwords changing them all is a bit of a pain, but not too big a deal. I'm just replacing one random string of values with another. I could change all my accounts in a weekend and all the new passwords are synced across my devices.
Lastpass is extremely convenient and I don't know of many practical alternatives that are any more secure against the same threat models. Maybe a piece of paper in my pocket would be more secure against the remote attacks, but I don't really see that as a step up.
Have you ever considered eating your own turds?
I am suspicious. My Capital One account was breeched two weeks ago using my online sign-in. I have a very long, random character password. The only way this could have been obtained is by malware on my computer, or it was obtained from LastPass.
Not to be too snobby, but I have a Mac that is pretty well locked down and only I use it. I am pretty sure the machine is clean. I do not trust LastPass at this point, and am changing all of my passwords and will discontinue my use of LastPass or any other solution like it. It's just too risky.
And if your Lastpass account is ever hacked you'll lose access to all those accounts. Better to come up with a simple algorithm to generate your password based on the site you're using. No need to store anything. One less 3rd party knowing all the sites you care about. One hack required per account. Automated hacking and data mining tools aren't going to understand your algorithm. A human might, but if you're being specifically targeted at that level you're going to lose anyway.
This happened three or four years ago too. I thought lastpass was great until that. I shut my account down immediately. They had a lot going for them, but security wasn't one of them.
In fact, when I wanted to demo about half a dozen dual-factor solutions for a colleague, I showed them all on my LastPass account.
There's always this: http://www.passwordcard.org/en
On a totally different note, I would propose websites implement a two-password system. One that allows logging in as normal, and one that allows changing everything. The changing-everything password would be kept securely somewhere, perhaps a safe deposit box.
Guys, what is your problem? The only way these guys have ANYTHING is if you use your master password on an actual website other than just logging into your lastpass account. Now, if your master paswoord is boobies, then, you're in trouble. But if you use anything remotely decent, you are fine. Especially if you use 2 factor authentication any time you login outside your known trusted devices the diminishing returns are so low... And unlike most companies, at least LastPass has the integrity to actually tell us when there has been a problem. You know, because that's something that responsible companies SHOULD DO. But mostly, they DON'T.
I am also a LastPass user and I understand how it works. I'm not particularly worried about this. Going to change the master password anyway (it's about time I did)
I wonder how many in the password col came out as -> salt+hash(salt +'CorrectHorseBatteryStaple')
This: rezial.com I admit that I never tried LastPass, so I'm not claiming this is better/more convenient.. I use it, and I'm happy with it. but now I also want to try LastPass :)
Would bcrypt be any better than PBKDF2 here?
Bcrypt is more computationally expensive than PBKDF2 (or SHAcrypt for that matter). The only thing more expensive is scrypt.
This: rezial.com
I admit that I never tried LastPass, so I'm not claiming this is better/more convenient.. I use it, and I'm happy with it.
but now I also want to try LastPass :)
Will that auto-fill password forms? Also, how is it any more secure? You're still encrypting your password list and storing it on somebody else's server - if somebody obtains the encrypted list they can attempt to brute-force it.
And if your Lastpass account is ever hacked you'll lose access to all those accounts.
Well, you can keep backups but obviously if they brute force your encryption key then they can log into all your accounts and change your passwords on you.
Better to come up with a simple algorithm to generate your password based on the site you're using. No need to store anything. One less 3rd party knowing all the sites you care about. One hack required per account. Automated hacking and data mining tools aren't going to understand your algorithm.
That has a few challenges:
1. The algorithm needs to be secure. That likely means you can't do it in your head. It probably also means that you'll want to use a standardized tool which is secure.
2. You need to be able to run the algorithm from any device you want to access a website from.
3. If you want auto-fill of password forms (a major timesaver with lastpass) then you need to write a fairly robust application for multiple platforms, which means you'll probably use the same program to run your algorithm everybody else uses.
4. Your algorithm needs to take into account that a single domain could have multiple passwords, and multiple domains could use a shared password. Again, sounds like a robust tool is needed.
5. Using standardized tools means that automated brute-forcing becomes a possibility.
6. Depending on the algorithm, obtaining the password for one site might allow an offline brute-force attack on the algorithm which could yield your other passwords.
I will agree that one advantage of this sort of approach is that there is no cache of passwords to crack, which means that you have to attack the individual websites which generally means an online attack (throttled, limited attempts, etc). However, see #6 above.
There's always this: http://www.passwordcard.org/en
As mentioned, writing down your passwords (which this is just a fancy version of) makes them harder to crack online, but opens you up to a different set of attacks, especially any that involve physically overpowering you.
You are assuming that LastPass did everything exactly as they describe; without typos, bugs, mistakes and backdoors.
My master password is 21-characters long. Even with the hashes having been collected, wouldn't it still take this side of forever to brute-force it? Should I still change my master password?
I'm really a low 5-digit Slashdotter, but this ID is where I am now.
Humans are a strange lot. We eagerly hand over our most prized data to programs and companies with abandon. Why? It's really not worth the convenience. I'm not a rocket scientist by any means, but I easily remember almost 50 passphrases to various and sundry things. None of them are easy to guess, none of them are the same. It's not terribly diffucult. The Internet has seen a dramatic rise in people handing control to other people and computers. It's really going to come back and haunt us. Disclaimer: I've been in IT for three decades, so I see the big picture. I don't understand the ease with which people are cavalier with their secrets.
Eggs and Baskets, I've been saying it for years.
Protecting all your different passwords with one password is fucking nonsensical. And hosting the encrypted (sic) file on the cloud is doubly so.
Lastpass is extremely convenient and I don't know of many practical alternatives that are any more secure against the same threat models.
Keepass with sync to a Google account. Gives you everything Lastpass Premium does for free, and it's more secure to boot. 2FA is free with Google accounts (no need to buy additional hardware), sync to mobile devices is free, and by not running in the browser and allowing you to use an optional keyfile as well as a master password it's more secure.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Better LastPass, than some alternative that doesn't disclose events like this.
The algorithm can be:
{ 12+ digit alphanumeric gibberish }{ short intuative code for the sight }{0-3 digit random affix used to shut up the sites mandatory reset rules }
They won't get it with a dictionary attack because it contains no words or common sequences. They won't get it by brute force because it's long 9and you can make it longer if it suite you to do so), And thy can't replay it to get other sights if they only have the one password.
To compromise more than one site with this password you need to us the one you have as the basis for a dictionary attack against other sites. And that can be complicated by using a less obvious site identifier. Say "fb" for "facebook" so an example Facebook pasword might look like:
bL2Y0CEYBybvfb030
and a hypothetical bank password might look like:
bL2Y0CEYBybvbk001
That's easily enough to make your password not the low hanging fruits in any given attack, and probably secure enough that you'd need to worry more about customer support being duped into resetting it for the attacker, or a MitM attack getting it in the clear than it being compromised from a hash, or from one of your compromised passwords on an other site.
As I said specifically said "I'm not claiming this is better". Just replying to OP wrt to existing alternatives.
Brute force? I would argue that by the time they broke it became irrelevant.
Lastpass is extremely convenient and I don't know of many practical alternatives that are any more secure against the same threat models.
Keepass with sync to a Google account. Gives you everything Lastpass Premium does for free, and it's more secure to boot. 2FA is free with Google accounts (no need to buy additional hardware), sync to mobile devices is free, and by not running in the browser and allowing you to use an optional keyfile as well as a master password it's more secure.
Well, it is missing support for ChromeOS (which also requires running in the browser). :)
And I don't really see it as any more secure. Somebody can hack into Lastpass, and somebody can hack into Google. Both are likely fairly robust with their security. Apparently Lastpass is fairly up-front about intrusions.
And nothing prevents you from using a keyfile with lastpass. Just copy/paste it into the password prompt right after typing in your memorized portion of the password. :)
I'd say that keepass is at best equivalent to lastpass if you're able to access the passwords from multiple systems, and if you don't implement it well you could be worse off.
Most of my computer friends write down the passwords but alter them in some pattern that works in their head. So ShittyIceCream8456 is ChapmansIceCream5684