Re: brute-force estimation
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: 22 Feb 2006 17:30:22 GMT
"Joseph Ashwood" <ashwood@xxxxxxx> writes:
"Elenhil" <elenhil@xxxxxxxxx> wrote in message
news:1140599172.853058.63330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Say, I have a 20 character long password consisting of latin
characters (capital and lower-case), numbers and basic punctuation.
That is roughly 80 symbols to play with.
How many combinations one must look through from 1 to 20 (the exact
length is unknown) with unoptimized brute force?
the answer is (80^20)/2 or safe by any means. That assumes you pick the
password randomly, for example using a pair of dice. I'm sure you can figure
out where I plugged the numbers in.
Generally we base our compliexity decisions based on an estimated largest
network it would be possible to build, and the timeframe. Right now the
generally agreed on (which I disagree with because we've left it the same
for over a decade) complexity required for near term security (<10 years) is
2^80. For medium term (<50 years) security the number usually quoted is
2^120+, and for long term (basically forever) 2^256.
My personally preferred method for generating secure passwords is a
derivative of Diceware (www.diceware.com) where I simply assign a-z and 0-9
to the roll of a pair of dice (two different colors, read the same one first
always), 36 is close enough to 32 that I can count each character as 5 bits,
and tune the security level very easily. This doesn't work too well on an
old UNIX system, but in modern systems where some [person] decided that a
space is not a valid character for a password it works well.
Joe
Just run a string of n random bytes (eg from /dev/urandom) through
uuencode, and you have 64 characters random string passwords.
.
- Follow-Ups:
- Re: brute-force estimation
- From: Joseph Ashwood
- Re: brute-force estimation
- From: Joseph Ashwood
- Re: brute-force estimation
- References:
- brute-force estimation
- From: Elenhil
- Re: brute-force estimation
- From: Joseph Ashwood
- brute-force estimation
- Prev by Date: Re: brute-force estimation
- Next by Date: Re: brute-force estimation
- Previous by thread: Re: brute-force estimation
- Next by thread: Re: brute-force estimation
- Index(es):
Relevant Pages
|