00:00
00:00
Skeik
Matthew @Skeik

Age 32, Male

Developer

University of Toledo

Ohio

Joined on 6/19/05

Level:
17
Exp Points:
2,944 / 3,210
Exp Rank:
20,024
Vote Power:
5.88 votes
Audio Scouts
1
Rank:
Safety Patrol
Global Rank:
25,284
Blams:
60
Saves:
333
B/P Bonus:
6%
Whistle:
Bronze
Trophies:
6
Medals:
812
Supporter:
10y 10m 8d

Passwords requiring a number (Math), not wearing pants

Posted by Skeik - March 3rd, 2010


Doesn't requiring a password to have a number in it actually decrease the different combinations of characters that make up passwords? Consider this.

Each password can be, uh, lets say there are 60 characters on a keyboard that can go into a password (There's probably more, this is talking about case sensitive, with numbers and symbols allowed) So if a password requires that you have uh, lets say 6-8 different characters in it, then these are the amount of different passwords possible.

(60^6)+(60^7)+(60^8) = 1.70807616 × 10^14 (Thanks google calculator)

The amount of possible passwords. Okay, that's cool and all, but this is without the crazy number restrictions. If we go back, and count the possible passwords when limiting one digit to be a number 0-9, this is what happens. According to probability, the easiest way to do this is to subtract all the possibilities of passwords that don't contain numbers whatsoever. That would be 50^6 or 50^7 so on, so forth for each length of password. Because there are 60 possibilities for each character in the password, and there are 10 numbers, we just subtract 10.

((60^6)-(50^6) )+((60^7)-(50^7) )+((60^8)-(50^8) ) = 1.30948241 × 10^14

That's not extremely significant but it's still a loss. Which means that it would be easier to brute force a password of this type. Especially since most people just put a 1 at the end of their password when required to put numbers in. I know, no one REALLY brute forces passwords but this just makes it easier for them if they wanted to. It's best to just allow the person to put their password in and SUGGEST that they put a number in, or at least, it makes sense to me. If there is something wrong with my math tell me.

This is just something I was thinking about lol.

Also I was just thinking about how I never made anything for Newgrounds. I mean, I have a few movies that I only uploaded here but those are shit. I really should make something for Pico Day, even if it's small. I'll try and think of something.

And Shark City and that Bow Game are coming along. I'm gonna post a screenshot of Shark City. If you're gonna say something about how it looks like Miami Shark, go ahead and say it, but I don't really care.

Passwords requiring a number (Math), not wearing pants


Comments

It makes it slightly easier to brute force a password.
However, brute force takes an age anyway, and with websites such as Newgrounds performing a 3 failed attempts lockout rule, a brute force is completely non-viable.

What the number system does prevent is a dictionary attack. Many people just use an English word for a password, and that cuts out a lot of possibilities. Forcing people to add at least one number makes a dictionary attack impossible (unless they program it to put in [dictionaryword+"1"], but it still does a good job of protecting those who don't just put a one at the end).
Again, sites with an attempt limit still won't be beaten by it, but then it also makes more difficult several other strategies (eg. people who decide to put their password as their favourite food or game character, or those who would otherwise use the same password for every site).

Also, nice pic!

Apologies for the lack of clarity; in the third paragraph I was saying that passwords on sites with attempt limits would not be beaten by dictionary attacks, yet still the 'one number rule' makes other tactics for breaking into a person's account less effective.

Also, how do sharks swim in a city?

I understand what you're saying. Would using brute force to figure out a password be good for any situation?

And lol, this is one badass Shark.

Of course there are some situations where brute forcing will be useful!
Obviously a 3 character password would be no problem. Also, if the information contained by the password is valuable and you have the time, brute force would be good.
But that would be a fair amount of time, I imagine.

And then you have several ways to speed up the time. Internet speed, parallel processing, etc.. Some brute-force attacks rely on using a large amount of zombie computers - computers which have been taken over by viruses, trojans and the like in order to perform an action such as a brute-force attack on a password, often without the owner knowing.
And, like I mentioned, dictionary attacks are still brute-force, but decrease the amount of attempts by a huge amount. As well as this, someone with access to a lot of user passwords (like Newgrounds admins) could create a list of common passwords, and attack other sites using brute force with this list of common passwords.
Anything is possible for an attacker with sufficient ability and resources and I'm sure people have come up with a load of different and increasingly effective ways of getting into a stranger's account.

In short, none of us are safe. We should all hide underground in our metal bunkers where we can protect ourselves from the internet terrorists.

*Head Explodes*

Have you ever thought bringing this point up to web-designers of sites that this information would apply to?

Well I mean Doomsday makes a good point too. My idea only applies in a situation where someone wants to brute force a website without eliminating any other possibilities. That could take days, weeks, or months to compute. But it does stop dictionary attacks, which could take a considerably lower amount amount of time.

It also stops people who have personal info on you finding your password, if you make it your mother's maiden name or something.

While you do have a point, I think the real issue here is enforcing stupid arbitrary maximum password lengths. For example, I won't use a password any shorter than 10 characters. Assuming I only use letters, my password is only one possibility out of a minimum of 52^10 (or 144,555,105,949,057,024 (that's 144 quadrillion), assuming a mix of upper- and lower-case letters). By restricting me to only 8 characters, my total possibilities are reduced to a maximum of 52^8, or 53,459,728,531,456 (or 53 trillion, ignoring valid passwords of six or seven characters). That's an entire order of magnitude, and with disk space being so cheap and abundant (and passwords requiring so little space to store) it seems criminal to me to impose arbitrary limits like this.

But I digress; you do have a valid point in terms of brute-forcing-- this method does indeed thwart dictionary-type attacks.

Something else you probably should think about it the extra possibilities a forced number imposes - that's an extra 10 CHARACTERS to cycle through per space. So, for example, in an 6 character password, if you were only to use lower case there would be 308,915,776 (26^6) lower and upper case is a whopping 19,770,609,664 (52^6). Then, adding the number requirement as well - 56,800,235,584 (62^6).

Adding in number drastically INCREASES the difficulty of cracking a password, because the hackers don't know if there's just 1 number or more. Assuming the hacker knows this seems a bit strange, because if they did, they probably wouldn't have to brute the whole thing anyway.

Also, in the case of users simply adding a 1 to the end of the password, that too is a good thing. It may be simple to guess, but it ads another whole POWER of digits (along with an extra 10 characters) that the hacker must cycle through.

So, no, in the case of brute forcing (and, really, any other type of hacking), it makes the cracking much more difficult when there is a forced number present.

What I'm saying is that when you tell the user he has to put at least one number in the password, it rules out every possibility of a password that doesn't contain a number. The hacker doesn't know if you had a number in your password in the first place, but by making it forced, the hacker would know that at least one of the character spaces must contain a number, so he can just throw away all the other possibilities that don't contain just one number, like I demonstrated in my post.

What you're saying is that forcing a number = the possibility of a number. But forcing a number means that the number is forced. A password on any website has the possibility of containing numbers, which is the situation you presented in your comment, but it's an entirely different situation to force a number.

And any hacker can know if a website is forcing a number on a password because of the fact that anyone who registers (on a public registration) would be able to figure that out.

But on a website where the number is not forced, the hacker will not use numbers to crack passwords, because there will be an abundance of accounts that will not use them. This will make their hacking much, much easier.

There the hackers can choose to create a cycle using only 26 characters, a system which they can practically fly through in comparison.

By making sure they know they'll need the full 62 cycle, that's going to hurt them. In the case of a dictionary, they can indeed throw out a number of options, but that is worse for them because they have a much lower chance of guessing.

So I do see what you're saying, with hackers who don't cycle through the full characters being less likely to hack well protected accounts, but it also gives them a huge amount of other, weaker accounts to break down. In the case of having forced numbers, though, accounts are almost equally protects (not counting length, cases, and difficulty of passwords).

Yes, the hackers will start with the full array to search with, meaning they'll find a password quicker than cycling through all letters and then all letters and numbers, but that's just ridiculous. The chances of a hacker being that stupid are much smaller than them getting into a poorly protected account with a readily available 26 character cycle.