|
Authored by: SilverWave on Tuesday, August 21 2012 @ 06:34 PM EDT |
Sites:
No, SHA1 is not a secure hashing algorithm
Use SHA512crypt, Bcrypt or PBKDF2.
Use a salt.
---
Users:
Don't reuse passwords between sites.
If you want use some kind of pattern *DONT* but if you do... at least use
something 14 characters long.
---
RMS: The 4 Freedoms
0 run the program for any purpose
1 study the source code and change it
2 make copies and distribute them
3 publish modified versions
[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Tuesday, August 21 2012 @ 08:35 PM EDT |
Yes you can "crack" a password quickly if the hash is known, is
produced via a quick insecure algorithm, and isn't salted. So ... beef up
security for hash tables, use secure algorithms, and apply a dose of salt.
Millions of individuals all struggling to think up longer and more unlikely
passwords and phrases isn't a good solution. Better security around hashing and
hash tables is more likely to have an impact.[ Reply to This | Parent | # ]
|
|
Authored by: nsomos on Tuesday, August 21 2012 @ 09:04 PM EDT |
For your consideration ..
https://www.grc.com/haystack.htm
Determines how large the search space would be for any given password.
Everything is done locally. The point is made that one of the most
important factors is how long the password is. Simply padding can
do wonders for making a password harder to crack.
There are also a number of password related links at bottom of that page.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Tuesday, August 21 2012 @ 09:43 PM EDT |
Some time ago I posted to the effect that using the first letters of each word
of a passage you've memorized can produce an easy to remember but quite long
password. For example.
IPATTFOTUSOAATTRFWISONUGIWLAJFA
Those 31 letters come from the US pledge of allegiance; I used it because it's
"obvious."
Those of you who may have memorized parts of the Aeneid in school have a good
place to start. Or maybe you played Algernon Moncrieff in a school production
of The Importance of Being Earnest and remember some of the dialogue ...
whatever.
The point is that searching World, or European, or even English literature,
textbooks and speeches for passages of 30 words or more is more trouble than
it's worth for any but the three letter agencies.
Marketer[ Reply to This | Parent | # ]
|
|
Authored by: cjk fossman on Wednesday, August 22 2012 @ 01:23 AM EDT |
As others have pointed out, this scenario assumes that the
criminal has gotten the user ids and passwords.
As far as I know, there are only two ways to accomplish this
feat: SQL injection and rooting the server.
For SQL injection, the two RDBMS's I know about provide a
simple and effective means of prevention. Any programmer
who fails to escape user input by these means should be
expelled from the guild and his or her head impaled on the
pike next to the city gates as an example to others.
Keeping the bad guys from getting root is more complex.
Even a sysadmin who follows the best practices *could*
become a victim. Even so, the best practices should be
sufficient unless you have a very determined criminal
knocking at the door.
And by the way, let's drop this pedant's war over "hackers"
vs. "crackers" and call them what they are: criminals. [ Reply to This | Parent | # ]
|
- Scary stuff, but - Authored by: Anonymous on Wednesday, August 22 2012 @ 04:28 AM EDT
- SQL injection is stupid. - Authored by: jesse on Wednesday, August 22 2012 @ 07:35 AM EDT
- Criminals? I'd think not. - Authored by: stegu on Wednesday, August 22 2012 @ 08:12 AM EDT
- NO - Authored by: scav on Wednesday, August 22 2012 @ 08:57 AM EDT
- NO - Authored by: cjk fossman on Wednesday, August 22 2012 @ 10:55 AM EDT
- NO - Authored by: Anonymous on Wednesday, August 22 2012 @ 11:02 AM EDT
- NO - Authored by: cjk fossman on Wednesday, August 22 2012 @ 12:49 PM EDT
- Bit of a Worry Then? - Authored by: Anonymous on Wednesday, August 22 2012 @ 04:39 PM EDT
- NO - Authored by: Anonymous on Thursday, August 23 2012 @ 11:29 AM EDT
|
|
|
|