News for hackers. Stuff that matters.
Re:LinkedIn password leak by wglb on Thursday May 19, 2016 @04:43PM (#11733666)
1: Change your password. RIGHT NOW. If you’re not sure how strong your password is, test sample passwords with our password checker here. Seriously?

Keep in mind that these estimates are based on some bogus entropy estimation. If a password hacking guy runs the correct dictionary past the hashes you password generates, it might be as small, well, as the first one tried. For example, run the passphrase Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn1 past the kaspersky bruteforce estimator, you get 10,000 centuries. But this is clearly false, as inicated in http://arstechnica.com/security/2013/08/thereisnofatebutwhat.... They clearly "cracked" this in far less time: "in a matter of minutes".

Re:LinkedIn password leak by saidajigumi on Thursday May 19, 2016 @04:57PM (#11733775)
As an aside, it can be so difficult to get this across to folks who aren't in the infosec headspace. I've seen even technical, computer science types absolutely not get that their ad-hoc memorable password "but no one would EVER guess that!" schemes are probably much more vulnerable than they estimate. Nevermind, even, true computing laypersons.
Re:LinkedIn password leak by ben_jones on Friday May 20, 2016 @01:06AM (#11735651)
We have to rotate our password advice to family and friends every couple years or so. It used to be "use a random combination of memorable words with a number thrown in" a la "reddogbarkhard7". Now I feel like right after guessing the 10k most common passwords a hacker would immediately brute word combinations with a single integer ending.
Re:LinkedIn password leak by yoha on Friday May 20, 2016 @02:29AM (#11735878)
The worst bias is letting the users choose their passwords. They should use a generator such as [1]. The reason is that the "entropy" is not a characteristic of a password but of the way it is generated. Computers are much better at entropy than humans.

[1] http://passwordcreator.org/

Re:LinkedIn password leak by Ntrails on Friday May 20, 2016 @04:43AM (#11736348)
Work sent around a stupid cardboard stand which was supposed to tell us all about being excellent at our work, and the checking processes required before sending anything to clients etc etc.

We were changing domains at the same time, so my new password root is now based on the first three characters of the first 3 lines of the thing, which included some punctuation, then the standard numeral to increment every 90 days.

My password was in plain sight for a couple months before I got around to binning it, which actually makes life a lot easier. Especially when you're not using it often enough for it to be muscle memory - which is the problem my parents face.

Re:LinkedIn password leak by yoha on Friday May 20, 2016 @05:40AM (#11736574)
However, such an approach corresponds to a few dozens bits of entropy at best (some for the approach, some for the length of text used, and a few for the numeral depending on whence it comes).

As stated by zamalek, the trick to not memorizing many passwords is to use a password manager.

Re:LinkedIn password leak by zamalek on Friday May 20, 2016 @03:49AM (#11736125)
Or, better yet, a password manager. If you aren't using one yet, now is a great opportunity.
Re:LinkedIn password leak by yoha on Friday May 20, 2016 @05:43AM (#11736583)
I agree that password managers are great. They let you use completely different passwords for each service, efficiently mitigating any compromise. Also, they tend to encourage you to use actually random passwords (using a generator).

However, most users will not bother, and getting them to use at least decent passwords would be a great step forward. Additionally, you still need a master password for your password manager.

Re:LinkedIn password leak by ben_jones on Saturday May 21, 2016 @12:26AM (#11743201)
Also you can't really rely on a free password manager (which is what users will generally select) to be a long-time solution. Either because they go out of business, change their monetization model, get hacked, whatever. It's one of those things that sounds good, but in reality is unable to gain critical mass for human reasons.
Re:LinkedIn password leak by wglb on Friday May 20, 2016 @08:00AM (#11737074)
What could possibly go wrong: This page was served over an insecure connection. It could have be forged or altered in transit. In red letters.

There is a certain degree of trust that non-technical users are asked to do that should leave us with at least a mild level of discomfort.

Re:LinkedIn password leak by joepie91_ on Friday May 20, 2016 @06:56AM (#11736866)
I've found that it helps to, rather than going directly into the mathematics of it all, explain to somebody that their password is going to be cracked by a computer rather than a human, and computers 'think differently'. Thus, you need to make things that seem complex to computers, not things that seem complex to humans.

The same applies verbatim for people trying to roll their own 'clever' encryption schemes.

Re:LinkedIn password leak by ashitlerferad on Friday May 20, 2016 @02:12AM (#11735828)
The only sane schemes are ones that choose passphrases solely based on entropy. So, Diceware or other random generation systems.
Re:LinkedIn password leak by scoot on Thursday May 19, 2016 @06:24PM (#11734348)
>> test sample passwords with our password checker

> Seriously?

Sample passwords, not your actual passwords.

If you follow that link, they reinforce that with: "Never enter your real password".

Re:LinkedIn password leak by wglb on Thursday May 19, 2016 @07:06PM (#11734550)
Yes, that is the actual instructions that they give.

Imagine a relative of yours who is much less computer savvy than you are. What are the chances that the actually enter their real password?

And what value is this check, actually, on a fake password. "Your fake password will take xxx centuries to crack". So how does the non-tech savvy person, who might have a struggle coming up with a real, useful password, then enter one that is similar but not exact and expect a measured response?

So even if they collect "simulated" passwords, password cracking is less about entropy and more about generating dictionaries based on patterns that users are likely to use.

There isn't any value in such a site, and I claim it is less than useful.

Re:LinkedIn password leak by dclowd9901 on Friday May 20, 2016 @01:39AM (#11735734)
Ok... 10,000^4 * 10 = 100,000,000,000,000,000 @1,000,000,000,000 passes per second (nsa level bruting) = 27 hours to break one single password. There's far more low hanging fruit in an encrypted list of passwords than to bother with random common word combos. Unless you're a specific target, it's not lucrative to a hacker to use brute forcing to get through the last 10 or 20% of users with good passwords.
Re:LinkedIn password leak by fnordsensei on Thursday May 19, 2016 @05:16PM (#11733925)
So, being one of the people who hovers around laymanship when it comes to these questions, how hard is it to crack a randomly generated 25 character string with 5 digits and 5 symbols? This is typically what I would use for a website.
Re:LinkedIn password leak by garethrees on Thursday May 19, 2016 @06:02PM (#11734218)
Such a password has about 157 bits of entropy, which is far too big to be found by any kind of brute-force approach.

Of course there are other ways that a password can be cracked, for example an attacker who breaks into the server can capture it as it is submitted. So it's still worth having a different password for each site.

Re:LinkedIn password leak by Freaky on Thursday May 19, 2016 @06:56PM (#11734499)
> Such a password has about 157 bits of entropy, which is far too big to be found by any kind of brute-force approach.

To put this into perspective:

If you turned every grain of sand on Earth (about eight quintillion) into a computer able to test 1 trillion passwords per second, you'd need about 360 million years to exhaust half the search space and have better than even odds of guessing it.

Re:LinkedIn password leak by wglb on Thursday May 19, 2016 @07:22PM (#11734625)
That is a good choice, and it is what I recommend to whoever will listen to me, and a few that won't.

I use and recommend 1Password. To evaluate a password manager, check this page https://discussions.agilebits.com/discussion/15416/1password... for good questions to ask. For example, what data they can turn over, what their encryption practices are. Key phrase: "There is no data of yours that we keep, so there is nothing to turnover".

This can't be said by all password managers.

Re:LinkedIn password leak by bad_user on Friday May 20, 2016 @01:09AM (#11735660)
That's an old and outdated page. 1Password has moved to a subscription model, thus storing the encrypted database themselves. The old "offline" option is still around, but it has been deemphasized, for one because they stopped implementing features supporting it (like an offline HTML interface for opvault, or sync with other clouds besides Dropbox). Even more upsetting is that the standalone version is now much more expensive than it was. They did that to increase the attractiveness of their subscriptions of course. And the writing is on the wall really.
Re:LinkedIn password leak by wglb on Friday May 20, 2016 @08:02AM (#11737080)
Well not quite. While they have added a subscription model, there is still the desktop-only version that works in accordance with that page.

I didn't notice an increase in their price--I have one at home and one from work.

Re:LinkedIn password leak by xapata on Thursday May 19, 2016 @11:00PM (#11735323)
Depends on how that password is stored. Mostly.

Your alphabet, lowercase + uppercase + digits + symbols, has 72 characters. There are 72 ways to pick the first character of your password, 72 ways to pick the second, etc. So there are 72 to the 25th power possible passwords, about 7.5 times 10 to the 46th (about 7 followed by 46 zeroes).

That's fewer possibilities than the number of atoms in the universe and fewer possibilities than the ways you can order a deck of cards, but if a computer can calculate one hash per nanosecond, it'd take about ... well, more millennia than I know the words for. Even if we're talking about a cluster of GPU machines, it's effectively forever. Unless you had some infinite improbability drive (like a quantum computer?) and you guess correctly on the first try.

So what did you use to generate the random password? Did you use your favorite programming language's pseudo-random number generator? Remember, "anyone who attempts to generate random numbers by deterministic means is, of course, living in a state of sin" (John von Neumann). A bad random number generator might only have 2^32 possibilities.

Let's put that aside. It's unlikely that the hacker knows which random number generator you used. It's much more likely that the company storing your passwords is not storing them securely. Passwords should not be stored, ever. Instead, the company should store a hashcode. The hashing algorithm should be like the butterfly effect -- a tiny change in the password produces an unpredictable difference in the hashcode. Unfortunately, many older hashing algorithms, like MD5, are predictable. A hacker can find an MD5 collision -- not your password, but one that hashes to the same hashcode -- within minutes.

There's more to it, but my advice is NEVER rely on password security by itself. If you care about your security, then use 2-factor authentication or physical security in combination with password protection.

Edit: Am I incorrect? I see there was a downvote. Please educate me.

Re:LinkedIn password leak by chronial on Thursday May 19, 2016 @05:22PM (#11733976)
How do you randomly generate these passwords?
Re:LinkedIn password leak by Esau on Thursday May 19, 2016 @07:02PM (#11734533)
Personally, I like to use Diceware to create random character strings.

http://world.std.com/~reinhold/dicewarefaq.html#randomstring...

I even bought a set of casino dice.

Re:LinkedIn password leak by beberlei on Thursday May 19, 2016 @10:56PM (#11735306)
you can install a tool "pwgen" on linux machines that will generate you passwords, configurable with size and types of characters included.

pwgen -y 40 1

Generates one password with 40 chars, including special chars (-y).

Re:LinkedIn password leak by pdw on Friday May 20, 2016 @04:04AM (#11736213)

    head -c 24 /dev/urandom | base64
will give you a password with 24 * 8 = 192 random bits.
Re:LinkedIn password leak by addled on Thursday May 19, 2016 @08:01PM (#11734795)
I like the password generator and virtual dice roller on https://www.random.org, but I guess it requires one to trust their claims that they are getting numbers from atmospheric noise and not a PRNG secretly.
Re:LinkedIn password leak by TheDong on Friday May 20, 2016 @12:41AM (#11735580)
More importantly, that's over the network so you have to trust the site to not log what it gives back, every CA to not have issued a false cert for them (allowing them to be trivially MITMd), and all software that runs on your computer to boot.

The "PRNG" vs "Real RNG" boogeyman scare is such a load of horseshit.

The whole point of modern PRNGs is that they're good enough computers can't detect patterns. I assure you that you're gaining zero security by using random.org vs openssl rand... and in fact, you're losing massive amounts of security because it's going over the network.

Re:LinkedIn password leak by throwaway7767 on Friday May 20, 2016 @08:38AM (#11737266)
Minor nitpick: you should replace "PRNG" with "cryptographically secure PRNG". Not all PRNG methods are aiming for the standard of "computers can't detect patterns", for example the common Mersenne Twister PRNG would not be a good choice to generate crypto keys or passwords.

You're right that using an internet service like that to generate passwords is insane, and there is no need for some fancy custom RNG hardware just to generate some keys/passwords.

Re:LinkedIn password leak by iimpact on Thursday May 19, 2016 @05:29PM (#11734028)
password managers
Re:LinkedIn password leak by sbierwagen on Thursday May 19, 2016 @06:22PM (#11734338)
Tinfoil hat time: if your password manager uses a bad generation scheme or backdoored RNG like Dual EC, then its passwords might be much easier to crack than they would appear.

https://en.wikipedia.org/wiki/Dual_EC_DRBG

Re:LinkedIn password leak by bigiain on Thursday May 19, 2016 @08:09PM (#11734827)
I know you covered yourself with the tinfoil disclaimer, but Ima take you seriously here for a thought experiment...

I wonder if that's actually a risk? At least for people not being individually targeted?

A random Elbonian hacker who gets a dump of 117 million password hashes has (at least) three approaches she can take to make use of it - she can run oclHashcat or JtR using a good wordlist (say, Hashkiller or phpbb) and a reasonable ruleset to tweak them, which'll fairly quickly reveal common, reused, or guessable passwords in hours/days/weeks - or she can set it to enumerate through an entire $howeverymany bit password space, which is guaranteed to find all the passwords but not before the heat death of the universe... Or she could try only the selections out of that random keyspace that a flawed version of FooPasswordSafe is capable of generating. I'm not sure how long the last approach would take, but it'd have to be both a pretty flawed PRNG and a very widely used password safe for it to come anywhere near as useful as approach 1.

(If she's only cracking the hash for the [email protected] record, things are somewhat different to if she's just trying to find _any_ "useable" passwords out of 117 million... And if she _knows_ sbeirwagen uses DudPasswordSafe.exe, it's likely she knows better ways of attempting to acquire your password than hoping to crack it from publicly released credential dumps...)

Re:LinkedIn password leak by dwightgunning on Thursday May 19, 2016 @07:01PM (#11734523)
This is always my concern. At some point the password managers become an interesting attack vector.

Why can't people just be nice.

Re:LinkedIn password leak by eru on Thursday May 19, 2016 @11:35PM (#11735409)
Do you actually generate your strings randomly, or do you rely on yourself, a puny human I suppose, to generate it?
Re:LinkedIn password leak by OhHeyItsE on Thursday May 19, 2016 @05:47PM (#11734130)
Aren't cracks of this nature thwarted by salting?
Re:LinkedIn password leak by ryanlol on Thursday May 19, 2016 @06:00PM (#11734211)
No. Salting mostly prevents rainbow tables from being very useful, but rainbow tables are questionably useful anyway with modern hardware. (Obviously depending on the type of the hash)
Re:LinkedIn password leak by OhHeyItsE on Thursday May 19, 2016 @06:11PM (#11734280)
Yeah but isn't this method just a giant rainbow table whose source is crawlable web content?

>It would have been impossible to use a brute-force attack or even a combined dictionary to crack a phrase of that length. But because the phrase was contained in this Wikipedia article, it wound up in a word list that allowed Chrysannthou to crack the phrase in a matter of minutes.

Re:LinkedIn password leak by wglb on Thursday May 19, 2016 @07:10PM (#11734568)
No, a rainbow table is just a method to pre-compute hashes. Given that you can, for $500 buy a graphics card that can compute seven hundred million hashes a second, precomputation is not really of any value.

The attack described is to find potential passwords on the web or somewhere, compute the hash, see if it matches. Rainbow tables aren't any part of this process.

Re:LinkedIn password leak by d_k_f on Thursday May 19, 2016 @07:20PM (#11734620)
This most likely depends on the way you look at it (or rather how exactly he did it): did he take the word list, generate hashes from it and then check them against leaked hashes? Rainbow table.

If he took the word list to run login attempts against a server (or a local endpoint checking the leaked database) it's more of a dictionary attack.

Same result, different ways to get there. If you're able to run your cracker locally against a leaked db, it probably doesn't really matter.