Choose your cart
Choose your cart
PASSWORD CREATING HELP TOOL
https://www.grc.com/haystack.htm
Had a Ball playing around with this
PASSWORD STRUCTURE 14 characters
4Symbols 3CAPITALS 3lowercase 4Symbols … IF YOU ARE ARTISTIC HAVE FUN WITH SYMBOLS P/O PWD
Time Required to Exhaustively Search this Password's Space:
Online Attack Scenario:
(Assuming one thousand guesses per second) 3.31 hundred trillion centuries
Offline Fast Attack Scenario:
(Assuming one hundred billion guesses per second) 3.31 million centuries
Massive Cracking Array Scenario:
(Assuming one hundred trillion guesses per second) 3.31 thousand centuries
Wow, and I thought I had a strong password.
Yours takes the cake!
Online Attack Scenario: (Assuming one thousand guesses per second) | 1.83 billion centuries |
Offline Fast Attack Scenario: (Assuming one hundred billion guesses per second) | 18.28 centuries |
Massive Cracking Array Scenario: (Assuming one hundred trillion guesses per second) | 1.83 years |
07-20-2014 10:50 AM - edited 07-20-2014 10:53 AM
Want to generate your own and not count on something off your machine?
Have excel or compatible?
Try using
=CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)&CHAR(RAND()*(127-33)+33)
Put in as many cells as you need as this is for eight characters randomly selected from all printable ascii (blank and control characters not included).
Some systems will accept all printable ascii and some will have some restrictions so you will have to see what rules apply for each.
You will of course not be able to remember these. And I tend to use 32 characters for critical systems. Using a system to store these for entry.
07-20-2014 11:58 AM - edited 07-20-2014 12:02 PM
I tend to use phrases or short sentences for the password if using ASCII
So "Eyes and Noes Feet and Toes" (my kid loves when I say that to her) might look like "3y3s and n03s feet and toes"
I say and type that enough where it doesn't take me that long to type in, and is amazingly secure. I don't use that, but as an example
If I did that, then my password looks like this
Online Attack Scenario: (Assuming one thousand guesses per second) | 14.38 trillion trillion trillion centuries |
Offline Fast Attack Scenario: (Assuming one hundred billion guesses per second) | 1.44 hundred thousand trillion trillion centuries |
Massive Cracking Array Scenario: (Assuming one hundred trillion guesses per second) | 1.44 hundred trillion trillion centuries |
07-20-2014 01:46 PM - edited 07-20-2014 01:48 PM
There are smarter password crackers that will try words and common substitues. The longer password may take longer. bit with valid or hidden words may not take as long. Truly random will take the longest.
FASCINATING !!
CAN YOU PLEASE EXPLAIN(BREAK DOWN) THE SYNTAX PART IN RED
CHAR(RAND()*(127-33)+33)
Lto\KTE| | |||||||||
)e8??Km% | |||||||||
.C>Ck#La | |||||||||
x}=lR<Y0 | |||||||||
"<Bub9CF | |||||||||
9YA!.]q: | |||||||||
]]jLrBge
| |||||||||
%k$/Ao'b | |||||||||
$Y;e_-p% |
07-21-2014 02:36 PM - edited 07-21-2014 02:59 PM
@TomH309 wrote:FASCINATING !!
CAN YOU PLEASE EXPLAIN(BREAK DOWN) THE SYNTAX PART IN RED
CHAR(RAND()*(127-33)+33)
Lto\KTE|
)e8??Km%
.C>Ck#La
x}=lR<Y0
"<Bub9CF
9YA!.]q:
]]jLrBge
Lto\KTE|
)e8??Km%
.C>Ck#La
x}=lR<Y0
"<Bub9CF
9YA!.]q:
]]jLrBge
%k$/Ao'b
$Y;e_-p%
%k$/Ao'b
$Y;e_-p%
IN ASCII the non-control characters are the decimal equivalent from 32 (a space) to 126 (Tilda). I skip space and ask for a random decimal number greater than or equal to 0 less than 1 and multiply by the range of printable ASCII chars and add the first non-blank 33 (happens to be a !)
I am little concerned by seeing repeated strings in your values. Something I don't thing I have seen.