Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Use a one-way hash like SHA1 or MD5, and use JavaScript to send the values as encrypted. Then, if a hacker intercepts the request, they would only have the hashes and not the actual values. They could still send the hashes to login, though; one solution is to include a JavaScript parameter (generated via your server-side language) based on IP (but not possible for a hacker to find the formula for), and use it to salt the username and password hashes.</p> <p>Then on server-side you would do (in PHP, in this case):</p> <pre><code>$ipHash = sha1("random" . $_SERVER['REMOTE_ADDR'] . "salt_here10381") // place this as a hidden element in the form and use it in the JavaScript to calculate the hash $userHash = $_POST['userHash']; $passwordHash = $_POST['passwordHash'] // TODO: Escape $ipHash, $userHash, $passwordHash $results = mysqli-&gt;query("SELECT * FROM `users` WHERE SHA1(CONCAT('" . $ipHash . "', `user`)) ='$userHash' AND SHA1(CONCAT('" . $ipHash . "', `password`)) = " '$passwordHash'"); </code></pre> <p>Then, if a hacker wanted to login with the hash and username they found, they would need the same IP of the user originally logging in whose credentials were intercepted.</p> <p>Note that this assumes you have passwords stored in your database as plain-text, which you should never do.</p> <p>For hashing with SHA1, on client-side, take a look at <a href="http://www.webtoolkit.info/javascript-sha1.html" rel="nofollow">this</a>.</p> <p>To answer your specific question (I see I got a bit off topic, oops,) it would be acceptable to base64encode the hashes when you send them to the server. If possible, try to send it as POST data and save it in a cookie or session variable.</p>
    singulars
    1. This table or related slice is empty.
    1. POSending encrypted text in Url
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris Kuehl
    1. USChris Kuehl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSending encrypted text in Url
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThe original question indicated the userID was a query param, which means it's needed to render the page and therefor needs to be decrypted. A hashing algorithm isn't going to solve an encryption problem.
      singulars
      1. PO
      1. USSnekse
 

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