Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds a lot like you're trying to implement some basic authentication. Something to try (in pseudo-code; I'm not great with Java on the web):</p> <pre><code>random_number = rand(1000000, 9999999); secret = "Some random text here"; timestamp = unix_timestamp(); // Get a UNIX timestamp user_ip = users_ip(); // Get the user's IP setcookie("random_number", random_number); // Save the random number setcookie("timestamp", timestamp); setcookie("token", sha256(random_number + secret + timestamp + ip)); // Concat and hash everything to form a token </code></pre> <p>When you want to check if the random number is valid, just pull all the pieces back together and compare it to the token:</p> <pre><code>random_number = getcookie("random_number"); secret = "Some random text here"; timestamp = int(getcookie("timestamp")); user_ip = users_ip(); // Get the user's IP token = sha256(random_number + secret + timestamp + ip); if(unix_timestamp() - timestamp &lt; 0 || unix_timestamp() - timestamp &gt; timeout) { // The token is more than an hour old; it might have been stolen. } if(token == getcookie("token")) { // The user is valid } else { // The user is invalid } </code></pre> <p>This code will block someone from spoofing the random number by making sure it comes from the same IP. You can also use the timestamp stuff to make sure that the user's session expires over time. This'll keep hackers from simply generating a good number and using it forever.</p> <p>As for the secret, that's a random text chunk. It should be completely random and never be shared. It basically makes your tokens virtually impossible to reverse engineer (otherwise, it's a matter of trying combinations like "number timestamp ip", "ip number timestamp", etc.).</p> <p>It should also be noted that something like this could be better accomplished with HMAC, but that could be somewhat overkill for what you're looking to do. This solution will do a damn good job as-is.</p> <p>Hope this helps.</p> <p><strong>EDIT</strong></p> <p>It should be noted that your secrets need to be the same for the verification to work.</p>
    singulars
    1. This table or related slice is empty.
    1. POImplementing a generation of HttpSession key
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmattbasta
    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. 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
    1. This table or related slice is empty.
 

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