I have a field (regular field, not a password) that is stored in the database twice: as a hash (SHA512) and as an encrypted value. Changing this setting will require many changes, which I do not want to insert. My question is: if the database is partitioned, does the fact that the field is stored twice as a hash and encrypted weakens its security? why?
Some people said yes because now they have 2 ways to possibly crack it. Spirit, I know that. What I am asking is can be used to crack another Lighter? Could the fact that the field has 2 options be anyway easier for an attacker to use to make cracks for others easier? Look at it this way: if the attacker is given only option A, he will take them for a day. If only option B is indicated, it will take 3 days. If the attacker launches both cracks independently, they crack open option A faster (it takes only one day). But if both are given to the attacker, they can crack one in just 6 hours. This is what I ask.
, , . , , : . (, PBKDF2), - , - , . , , .
, . , , , - . , , , , . , . :
, - . -.
"" ; / , . . . , , . , / , , , , , .
[]
( ), , http://en.wikipedia.org/wiki/Cryptographic_hash_function. , "". , , , .
, . :
, , AES-CTR IV.
. :
, , . , ? ( ).
, , , ( ).
, , . , .
, , , ? A 6 B 9 , , 4 ? ? , , , . SHA512 ( ) , ur . , . , . CPU Cycles, - . , 500- , . , , . LOL
A B? , , .
, 2 , - , ?
, , , , .
, . , - , , . .