The advice was direct to everyone to make it clear up an misunderstanding.Quote:
Not overcrypted though, but creating an own way will sure be more safe than use a generic one, so if your database might be broken, well, if don't use generic way it will be very impossible to descramble the password
You should read this article: [Only registered and activated users can see links. Click Here To Register...]
There is a chapter where they discuss "The WRONG Way: Double Hashing & Wacky Hash Functions"
I quote:
So basically just stick with a simple function because it's easy to reverse engineer, or figure out the function. Also I recommend using the mcrypt_create_iv function is good for generating random salts.Quote:
An attacker cannot attack a hash when he doesn't know the algorithm, but note Kerckhoffs's principle, that the attacker will usually have access to the source code (especially if it's free or open source software), and that given a few password-hash pairs from the target system, it is not difficult to reverse engineer the algorithm. It does take longer to compute wacky hash functions, but only by a small constant factor. It's better to use an iterated algorithm that's designed to be extremely hard to parallelize (these are discussed below). And, properly salting the hash solves the rainbow table problem.
I am still waiting for the developers to implement this.. I've to say they are really slow.. They might need to consider closing their private server since their don't have the team to manage it properly.