Databases
StackOverflow2013
Postsdbo
POEncryption/Hashing issues
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEncryption/Hashing issues
    primarykey
    data
    text
    <p>I'm working on a little script that will allow me to store relatively secure information in a cookie to validate a user login without the use of sessions. Part of the output is an encrypted salt to use when generating a hmac_hash with some of the information stored in the cookie, and some of the user information in the database.</p> <p>However, after some testing, I've ran into a problem with the encryption/decryption of the strings and causing different hash results.</p> <p>ie:</p> <pre><code>$str = '123456abcdef'; $hash1 = sha1($str); $v1 = do_encrypt($str); $v2 = do_decrypt($v1); $hash2 = sha1($v2); </code></pre> <p>and I end up with</p> <pre><code>$hash1 - d4fbef92af33c1789d9130384a56737d181cc6df $hash2 - 0d6034f417c2cfe1d60d263101dc0f8354a1216f </code></pre> <p>but when I echo both strings, they are both 123456abcdef.</p> <p>The do_encrypt function is as follows:</p> <pre><code>function do_encrypt($value) { $salt = generate_salt(); $td = mcrypt_module_open('rijndael-256', '', 'cbc', ''); mcrypt_generic_init($td, $ek, $salt); $encrypted_data = mcrypt_generic($td, $value); mcrypt_generic_deinit($td); mcrypt_module_close($td); return base64_encode($salt.$encrypted_data); } </code></pre> <p>The do_decrypt function:</p> <pre><code>function do_decrypt($value) { $data = base64_decode($value); $salt = substr($data, 0, 32); $data = substr($data, 32, strlen($data)); $td = mcrypt_module_open('rijndael-256', '', 'cbc', ''); mcrypt_generic_init($td, $ek, $salt); $decrypted_data = mdecrypt_generic($td, $data); mcrypt_generic_deinit($td); mcrypt_module_close($td); return $decrypted_data; } </code></pre> <p>for both functions $ek is an encryption key pulled from another file.</p> <p>I'm trying to understand why the characters that display are the same, but the actual variables are different (otherwise the hash results would be the same), and is there any way to ensure that both strings are identical for hashing purposes?</p> <p>Thanks, Ryan.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USitsreeyan
    1. USitsreeyan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEncryption/Hashing issues
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEncryption/Hashing issues
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBut you just said the encrypt generates a random salt, how do you know that salt when you decrypt it? And could you just show us the functions?
      singulars
      1. POEncryption/Hashing issues
      1. USBen
    2. COEncryption/decryption is not relevant in hashing, there is only hashing to match one hashed value to another generated hash value. Encryption `!=` hashing.
      singulars
      1. POEncryption/Hashing issues
      1. USJared Farrish
    3. CO@jaredfarrish I know the difference between the two. I am encrypting an additional piece to be stored in the cookie, that when it is retrieved, I can decrypt the value to use as the hmac salt.
      singulars
      1. POEncryption/Hashing issues
      1. USitsreeyan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload